Triple
T27373853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenshoe Road |
E690405
|
entity |
| Predicate | marksNorthernEndOf |
P15231
|
FINISHED |
| Object | Ontario Highway 404 |
—
|
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: Ontario Highway 404 | Statement: [Ravenshoe Road, marksNorthernEndOf, Ontario Highway 404]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksNorthernEndOf Context triple: [Ravenshoe Road, marksNorthernEndOf, Ontario Highway 404]
-
A.
locatedAtNorthernEndOf
chosen
Indicates that one entity is situated at or near the northernmost part or extremity of another entity.
-
B.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
-
C.
northernTerminusConnects
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
D.
northernTerminusNearbyPlace
Indicates that a place serves as, or is located very close to, the northern endpoint of a route, line, or similar feature.
-
E.
northernTerminusRegion
Indicates that a location or route has its northern endpoint or final stopping point within a specified region.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c63cfa88190a6f188ba8a63e809 |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:19 p.m.