Triple

T1638087
Position Surface form Disambiguated ID Type / Status
Subject James Millar E35402 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: [James Millar, familyName, Millar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Millar
Context triple: [James Millar, familyName, Millar]
  • A. Millar chosen
    Millar is a surname and variant spelling of Miller, commonly found in English-speaking countries.
  • B. 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.
  • C. Andrew Millar
    Andrew Millar was an 18th-century Scottish-born London bookseller and publisher known for issuing major works of Enlightenment authors, including David Hume.
  • D. Pierce
    Pierce is a surname most prominently associated with Paul Pierce, the Hall of Fame former NBA star of the Boston Celtics.
  • E. Kelleher
    Kelleher is a surname most notably associated with Herb Kelleher, the co-founder and longtime CEO of Southwest Airlines.
  • 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_69a88604618c81908b41f6429c431eb6 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90a1ac46081909f10e793898a9911 completed March 5, 2026, 4:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad79847cbc8190be99c66424034bce completed March 8, 2026, 1:28 p.m.
Created at: March 4, 2026, 7:28 p.m.