Triple
T9391993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Boyd |
E226046
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Millar |
E35402
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Millar | Statement: [Stephen Boyd, familyName, Millar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Millar Context triple: [Stephen Boyd, familyName, Millar]
-
A.
Millar
chosen
Millar is a surname and variant spelling of Miller, commonly found in English-speaking countries.
-
B.
Mullally
Mullally is a surname of Irish origin borne by various notable individuals in fields such as entertainment, sports, and public service.
-
C.
Alt Millars
Alt Millars is a rural comarca in the inland part of Spain’s Valencian Community, known for its mountainous landscapes, river valleys, and small historic villages.
-
D.
Kinnear
Kinnear is an English surname most notably associated with the British actor Rory Kinnear and his theatrical family.
-
E.
Mulally
Mulally is the surname of Alan Mulally, the American engineer and former CEO known for leading major turnarounds at Boeing and Ford Motor Company.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510eae0c8190b7c4ab487a366bb3 |
completed | April 1, 2026, 5:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1010169d88190a7267615a9196d4b |
completed | April 4, 2026, 12:16 p.m. |
Created at: March 30, 2026, 7:45 p.m.