Triple

T5146236
Position Surface form Disambiguated ID Type / Status
Subject Brent E116076 entity
Predicate contains P35 FINISHED
Object Tokyngton E415095 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: Tokyngton | Statement: [Brent, contains, Tokyngton]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tokyngton
Context triple: [Brent, contains, Tokyngton]
  • A. Tokyngton chosen
    Tokyngton is a residential district in the London Borough of Brent, known for its proximity to Wembley Stadium and its diverse local community.
  • B. Buckingham
    Buckingham is a historic parliamentary borough in Buckinghamshire, England, that long served as a constituency represented in the British House of Commons.
  • C. Buckingham
    Buckingham is a former municipality in western Quebec, Canada, now part of the city of Gatineau.
  • D. Tilbury
    Tilbury is a small community within the municipality of Chatham-Kent in southwestern Ontario, Canada, known for its agricultural surroundings and local services.
  • E. Tilbury
    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.
  • 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_69bd4446c0e08190a7c29dc74976bf03 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd78ac677881909ce8632f1a8af880 completed March 20, 2026, 4:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69becff590ec81908ed03474f21a95f5 completed March 21, 2026, 5:05 p.m.
Created at: March 20, 2026, 1:43 p.m.