Triple

T10908822
Position Surface form Disambiguated ID Type / Status
Subject Mullally E257639 entity
Predicate hasVariant P455 FINISHED
Object Mulally E47497 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: Mulally | Statement: [Mullally, hasVariant, Mulally]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mulally
Context triple: [Mullally, hasVariant, Mulally]
  • A. Mulally chosen
    Mulally is the surname of Alan Mulally, the American engineer and former CEO known for leading major turnarounds at Boeing and Ford Motor Company.
  • B. Kinnear
    Kinnear is an English surname most notably associated with the British actor Rory Kinnear and his theatrical family.
  • C. Mullins
    Mullins is an English-language surname of Irish and Norman origin borne by various notable individuals across history.
  • D. Mali Finn
    Mali Finn was a prominent American casting director known for discovering and launching the careers of numerous young actors in major Hollywood films.
  • E. Mullan
    Mullan is a surname of Irish and Scottish origin, often considered a variant of the name Mullen.
  • 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_69d6aa8550c8819095508a2ed9acf3db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d7706824d08190ba894d144cc6b3ba completed April 9, 2026, 9:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69e1554fc61c8190a0354e2f24cb62e4 completed April 16, 2026, 9:31 p.m.
Created at: April 8, 2026, 9:22 p.m.