Triple

T11493588
Position Surface form Disambiguated ID Type / Status
Subject Tilbury Fort E272475 entity
Predicate locatedIn P40 FINISHED
Object Tilbury E222850 NE FINISHED

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: Tilbury | Statement: [Tilbury Fort, locatedIn, Tilbury]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tilbury
Context triple: [Tilbury Fort, locatedIn, Tilbury]
  • A. Tilbury
    Tilbury is a small community within the municipality of Chatham-Kent in southwestern Ontario, Canada, known for its agricultural surroundings and local services.
  • B. Tilbury chosen
    Tilbury is a port town on the north bank of the River Thames in Essex, England, known for its docks and historic forts guarding the approach to London.
  • C. Isleworth
    Isleworth is a suburban town in West London, England, known for hosting major media and broadcasting facilities.
  • D. Berkhamsted
    Berkhamsted is a historic market town in Hertfordshire, England, known for its medieval castle remains and role as a commuter hub northwest of London.
  • E. Biddenden
    Biddenden is a historic village in Kent, England, known for its traditional Wealden architecture, vineyards, and the local legend of the Biddenden Maids.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85ddffdf88190a00e94ad5b8b91a5 completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69f018963218819097771032a88688af completed April 28, 2026, 2:16 a.m.
Created at: April 8, 2026, 9:36 p.m.