Triple
T8666378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burin Peninsula |
E205683
|
entity |
| Predicate | hasTransportation |
P105
|
FINISHED |
| Object | Route 210 |
E738483
|
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: Route 210 | Statement: [Burin Peninsula, hasTransportation, Route 210]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Route 210 Context triple: [Burin Peninsula, hasTransportation, Route 210]
-
A.
Route 210
chosen
Route 210 is a highway in Newfoundland and Labrador, Canada, that serves as a primary transportation corridor on the Burin Peninsula.
-
B.
Route 110
Route 110 is a poem by Seamus Heaney that reimagines episodes from Homer’s Odyssey within the landscapes and experiences of modern Ireland.
-
C.
Route 185
Route 185 is a numbered roadway that serves as a connector within the regional highway network linked to Route 440.
-
D.
Route 147
Route 147 is a numbered roadway that serves as a key connector passing through the Uruca area.
-
E.
Route 184
Route 184 is a numbered roadway that serves as a connector within a regional highway network, linking to other major routes such as Route 440.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48a1dd1481908c56abca48fcd562 |
completed | March 31, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecd1592788190a882fb7218f95807 |
completed | April 2, 2026, 8:09 p.m. |
Created at: March 30, 2026, 6:31 p.m.