Triple

T18101735
Position Surface form Disambiguated ID Type / Status
Subject Bulwell E433236 entity
Predicate locatedIn P40 FINISHED
Object Nottingham 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: Nottingham | Statement: [Bulwell, locatedIn, Nottingham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nottingham
Context triple: [Bulwell, locatedIn, Nottingham]
  • A. Nottingham chosen
    Nottingham is a major city in the East Midlands of England, historically known for its lace-making and bicycle industries and famously associated with the legend of Robin Hood.
  • B. Coventry
    Coventry is a historic city in England, best known for its medieval cathedral destroyed in World War II and its symbolic postwar reconciliation efforts.
  • C. Coventry
    Coventry is a town in central Rhode Island known for its suburban communities, historic villages, and extensive outdoor recreation areas.
  • D. Sheffield
    Sheffield is a small unincorporated community in West Texas known historically as a ranching and oilfield service town along the Pecos River.
  • E. Sheffield
    Sheffield is a small rural town in southwestern Massachusetts known for its scenic landscapes, historic charm, and location in the Berkshires.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddb6fed8819090798683353a5c08 completed April 19, 2026, 1:50 p.m.
Created at: April 10, 2026, 10:28 a.m.