Triple
T9417010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Highway 138 |
E227050
|
entity |
| Predicate | northernTerminusDirection |
P34413
|
FINISHED |
| Object | toward Ottawa |
—
|
LITERAL 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: toward Ottawa | Statement: [Ontario Highway 138, northernTerminusDirection, toward Ottawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernTerminusDirection Context triple: [Ontario Highway 138, northernTerminusDirection, toward Ottawa]
-
A.
northernTerminusConnects
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
B.
terminusDirection
chosen
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
C.
northernTerminusRegion
Indicates that a location or route has its northern endpoint or final stopping point within a specified region.
-
D.
northernTerminusCity
Indicates that one city serves as the northern endpoint or final stop of a route, line, or corridor relative to another location.
-
E.
northernTerminusMunicipality
Indicates that a municipality serves as the northern endpoint or terminus of a route, line, or similar linear feature.
- F. None of above.
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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd68cb4be08190a47f901a9703f9db |
completed | April 1, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.