Triple

T21760601
Position Surface form Disambiguated ID Type / Status
Subject Battle of Fort Henry E537152 entity
Predicate belligerent P375 FINISHED
Object Union 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: Union | Statement: [Battle of Fort Henry, belligerent, Union]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Union
Context triple: [Battle of Fort Henry, belligerent, Union]
  • A. Union
    Union is a major interchange station in the Dubai Metro system where key lines intersect, serving as a central hub for passenger transfers.
  • B. Union chosen
    The Union was the federal government and Northern states of the United States that opposed the seceding Confederate states during the American Civil War.
  • C. Union
    Union is the commonly used short name for the Major League Soccer club Philadelphia Union.
  • D. Union
    Union is a town in Broome County, New York, that forms part of the Binghamton metropolitan area.
  • E. Union
    Union is a major transit hub in downtown Toronto that serves as the city's primary subway and railway station complex.
  • 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_69e0c46f5d1c8190bf830409e98464e5 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01d91e9788190a11d0295306e78a4 completed April 28, 2026, 2:38 a.m.
Created at: April 16, 2026, 6:50 p.m.