Triple
T20234848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTH 101 |
E495622
|
entity |
| Predicate | connectsWith |
P37
|
FINISHED |
| Object | PTH 15 |
—
|
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: PTH 15 | Statement: [PTH 101, connectsWith, PTH 15]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PTH 15 Context triple: [PTH 101, connectsWith, PTH 15]
-
A.
PTH 15
chosen
PTH 15 is a provincial highway in Manitoba, Canada, serving as an important east–west route linking Winnipeg to communities to the east.
-
B.
PTH 1
PTH 1 is a major provincial highway in Manitoba, Canada, forming part of the Trans-Canada Highway and serving as a primary east–west transportation route across the province.
-
C.
PTH 14
PTH 14 is a provincial highway in Manitoba, Canada, serving as an important east–west route in the southern part of the province.
-
D.
PTH 100
PTH 100 is a major ring road route forming part of the Perimeter Highway system around Winnipeg, Manitoba.
-
E.
PTH 75
PTH 75 is a major Manitoba provincial highway that serves as the primary route between Winnipeg and the U.S. border at Emerson.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6716995b88190a8514b41232b0e94 |
completed | April 20, 2026, 6:33 p.m. |
Created at: April 11, 2026, 11:40 p.m.