Triple

T21760600
Position Surface form Disambiguated ID Type / Status
Subject Battle of Fort Henry E537152 entity
Predicate location P40 FINISHED
Object Fort Henry — 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: Fort Henry | Statement: [Battle of Fort Henry, location, Fort Henry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Fort Henry
Context triple: [Battle of Fort Henry, location, Fort Henry]
  • A. Fort Henry
    Fort Henry is a historic 19th-century British military fortress and popular tourist site located in Kingston, Ontario, Canada.
  • B. Fort Henry chosen
    Fort Henry was a Confederate stronghold on the Tennessee River whose capture by Union forces in 1862 marked a key early victory in the Western Theater of the American Civil War.
  • C. Fort Foote
    Fort Foote was a Union earthwork fortification built during the American Civil War to help defend Washington, D.C., particularly by controlling approaches along the Potomac River.
  • D. Fort Hancock
    Fort Hancock is a historic former U.S. Army coastal defense installation located on Sandy Hook in New Jersey, now preserved as part of Gateway National Recreation Area.
  • E. Fort Hancock
    Fort Hancock is a small unincorporated community in far West Texas near the U.S.–Mexico border, known for its rural desert setting and role as a local border crossing point.
  • 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.