Triple
T18111017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire Cup |
E433472
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | York |
—
|
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: York | Statement: [Yorkshire Cup, city, York]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: York Context triple: [Yorkshire Cup, city, York]
-
A.
York
York is a historic former municipality in Ontario, Canada, that is now part of the modern city of Toronto.
-
B.
York
York is a historic rural town in Western Australia’s Wheatbelt region, known for its heritage architecture and agricultural surroundings.
-
C.
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.
-
D.
York
York is a well-known global brand of heating, ventilation, air conditioning, and refrigeration (HVAC&R) equipment owned by Johnson Controls.
-
E.
York
York is a common English surname historically associated with the city of York in England and borne by various notable individuals and families.
- 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_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.