Triple
T30312585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 12 in North Dakota |
E770966
|
entity |
| Predicate | westernTerminusStateLineWith |
P29442
|
FINISHED |
| Object | Montana |
—
|
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: Montana | Statement: [U.S. Route 12 in North Dakota, westernTerminusStateLineWith, Montana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernTerminusStateLineWith Context triple: [U.S. Route 12 in North Dakota, westernTerminusStateLineWith, Montana]
-
A.
westernTerminusConnectsTo
Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
-
B.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
C.
westernTerminusDetail
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
D.
westernTerminusState
chosen
Indicates the state in which something (such as a route, line, or path) has its western endpoint or terminus.
-
E.
westernTerminusCrosses
Indicates that the western endpoint of a route, line, or path intersects or passes over another feature or boundary.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816ceb688190b2e5f01205f3c550 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:50 p.m.