Triple
T35151336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topaz Lake |
E1015000
|
entity |
| Predicate | hasBorderHighway |
P385
|
FINISHED |
| Object | U.S. Route 395 |
—
|
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: U.S. Route 395 | Statement: [Topaz Lake, hasBorderHighway, U.S. Route 395]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderHighway Context triple: [Topaz Lake, hasBorderHighway, U.S. Route 395]
-
A.
hasRoadBoundary
Indicates that a road segment is associated with a specific boundary or edge that defines its lateral limits.
-
B.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
C.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
hasBorderTrafficControl
Indicates that there is an official system or mechanism in place to monitor, regulate, or manage the movement of people or goods across a border.
-
E.
isDividedHighway
Indicates that a roadway consists of physically separated carriageways for opposing directions of traffic.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:02 p.m.