Triple

T1753387
Position Surface form Disambiguated ID Type / Status
Subject North Yorkshire E38497 entity
Predicate borders P224 FINISHED
Object York E29705 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: York | Statement: [North Yorkshire, borders, York]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: York
Context triple: [North Yorkshire, borders, York]
  • A. York chosen
    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.
  • B. York
    York is a historic former municipality in Ontario, Canada, that is now part of the modern city of Toronto.
  • C. 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.
  • D. Manchester
    Manchester is a major city in northwest England known for its industrial heritage, vibrant cultural scene, and influential contributions to music, sport, and science.
  • E. Lancaster
    Lancaster is a historic city in North West England known for its medieval castle, Georgian architecture, and role as the county town of Lancashire.
  • 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_69a8862bdb2081908aefe831c8aa8017 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa64169c508190a33074fb06e9c755 completed March 6, 2026, 5:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69add1b679d88190b3c6e50c96f917e4 completed March 8, 2026, 7:44 p.m.
Created at: March 4, 2026, 7:31 p.m.