Triple
T31033826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana Highway 15 |
E790802
|
entity |
| Predicate | isCrossBorderRoute |
P95603
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Montana Highway 15, isCrossBorderRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCrossBorderRoute Context triple: [Montana Highway 15, isCrossBorderRoute, true]
-
A.
isCrossBorder
chosen
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
B.
hasCrossBorderArea
Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
-
C.
isNonUSInternationalRoute
Indicates that a route is international and does not involve the United States as an origin, destination, or transit point.
-
D.
hasCrossBorderTrade
Indicates that there is trade or commercial exchange occurring between entities located in different countries or jurisdictions.
-
E.
hasCrossBorderCenter
Indicates that an entity operates or is associated with a center whose activities, services, or scope extend across national borders.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694c3e0f881909ea3548ec8ab3eaf |
completed | May 3, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.