Triple

T17393967
Position Surface form Disambiguated ID Type / Status
Subject Old Ford Locks E422900 entity
Predicate near P350 FINISHED
Object Old Ford 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: Old Ford | Statement: [Old Ford Locks, near, Old Ford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Old Ford
Context triple: [Old Ford Locks, near, Old Ford]
  • A. Old Ford chosen
    Old Ford is a historic district in East London, England, known for its industrial heritage and proximity to the River Lea and Victoria Park.
  • B. Ely’s Ford
    Ely’s Ford is a historic river crossing in Virginia that played a notable role in American Civil War troop movements and campaigns.
  • C. Boteler’s Ford
    Boteler’s Ford is a historic crossing point on the Potomac River near Shepherdstown, West Virginia, notable as the site of significant Civil War military action.
  • D. Blackburn’s Ford
    Blackburn’s Ford is a strategically important crossing point on Bull Run Creek in Virginia that played a notable role in the early stages of the American Civil War.
  • E. Sudley Ford
    Sudley Ford is a strategically important river crossing on Bull Run in Virginia, notable for its role in the First Battle of Bull Run during the American Civil War.
  • 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_69d889d710288190bf0f4762801fefae completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43abbd84881908af91bb7c9784026 completed April 19, 2026, 2:15 a.m.
Created at: April 10, 2026, 5:45 a.m.