Triple
T12744482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convict Lake Road |
E304569
|
entity |
| Predicate | closestHighwayJunction |
P31669
|
FINISHED |
| Object | intersection with U.S. Route 395 near Convict Lake turnoff |
—
|
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: intersection with U.S. Route 395 near Convict Lake turnoff | Statement: [Convict Lake Road, closestHighwayJunction, intersection with U.S. Route 395 near Convict Lake turnoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestHighwayJunction Context triple: [Convict Lake Road, closestHighwayJunction, intersection with U.S. Route 395 near Convict Lake turnoff]
-
A.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
B.
nearJunctionOf
chosen
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
C.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
-
D.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
E.
nearbyHighwayMilepost
Indicates that one entity is located close to a specific highway milepost associated with another entity.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.