Triple

T1916946
Position Surface form Disambiguated ID Type / Status
Subject Chorley E40038 entity
Predicate locatedNear P294 FINISHED
Object Manchester E114 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: Manchester | Statement: [Chorley, locatedNear, Manchester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Manchester
Context triple: [Chorley, locatedNear, Manchester]
  • A. Manchester chosen
    Manchester is a major city in northwest England known for its industrial heritage, vibrant cultural scene, and influential contributions to music, sport, and science.
  • B. Manchester
    Manchester is the most populous city in the U.S. state of New Hampshire and a major economic and cultural center for the region.
  • C. York
    York is a historic walled city in North Yorkshire, England, renowned for its medieval architecture, including York Minster, and its rich Roman and Viking heritage.
  • D. York
    York is a historic former municipality in Ontario, Canada, that is now part of the modern city of Toronto.
  • E. Birmingham
    Birmingham is a major industrial city in England’s West Midlands, historically significant for its manufacturing heritage and heavy bombing during the Second World War.
  • 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_69a8864298748190a2f2fd34f7ef8d77 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb20f54848190b9457e1231aa49db completed March 7, 2026, 5:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae0307ffac8190a9d335a975e88e9e completed March 8, 2026, 11:15 p.m.
Created at: March 4, 2026, 7:35 p.m.