Triple
T27833116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lund, British Columbia |
E703154
|
entity |
| Predicate | highwayTerminusDirection |
P34413
|
FINISHED |
| Object | northern terminus of Highway 101 |
—
|
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: northern terminus of Highway 101 | Statement: [Lund, British Columbia, highwayTerminusDirection, northern terminus of Highway 101]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highwayTerminusDirection Context triple: [Lund, British Columbia, highwayTerminusDirection, northern terminus of Highway 101]
-
A.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
B.
terminusDirection
chosen
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
C.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
-
D.
departureDirection
Indicates the direction or bearing in which an entity moves away from its point of origin or starting location.
-
E.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 5:57 p.m.