Triple
T407509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Canada |
E9414
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | York |
E36102
|
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: [Upper Canada, capital, York]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: York Context triple: [Upper Canada, capital, York]
-
A.
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.
-
B.
York
chosen
York is a historic former municipality in Ontario, Canada, that is now part of the modern city of Toronto.
-
C.
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.
-
D.
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.
-
E.
Lancaster
Lancaster is a suburban city in the Dallas–Fort Worth metropolitan area known for its residential communities and proximity to Dallas.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbd766c8190bb8a91605929156a |
completed | Feb. 28, 2026, 1:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4b8a6c0788190b38c563b5555ff90 |
completed | March 1, 2026, 10:07 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.