Triple

T20389319
Position Surface form Disambiguated ID Type / Status
Subject A Good Day to Die Hard E498043 entity
Predicate director P255 FINISHED
Object John Moore NE NERFINISHED

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: John Moore | Statement: [A Good Day to Die Hard, director, John Moore]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: John Moore
Context triple: [A Good Day to Die Hard, director, John Moore]
  • A. John Moore chosen
    John Moore is an Irish film director best known for helming big-budget action movies such as "A Good Day to Die Hard."
  • B. John Moore
    John Moore was an American statesman who represented South Carolina as a delegate to the Continental Congress during the Revolutionary era.
  • C. John Moore
    John Moore was a film art director known for his work on mid-20th-century historical epics such as the 1961 movie "El Cid."
  • D. John Moore
    John Moore was a distinguished British Army general of the Napoleonic era, best known for his reforms of light infantry and his leadership during the Peninsular War.
  • E. John Henry Moore
    John Henry Moore was a Texian military leader best known for commanding the rebel forces at the opening skirmish of the Texas Revolution, the Battle of Gonzales.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4a71ebc8190b153a36c738730f4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6790e65a081909832855758fffd14 completed April 20, 2026, 7:05 p.m.
Created at: April 16, 2026, 11:28 a.m.