Triple
T23565240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 90 in South Dakota |
E579352
|
entity |
| Predicate | isTranscontinentalRoute |
P111267
|
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: [Interstate 90 in South Dakota, isTranscontinentalRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTranscontinentalRoute Context triple: [Interstate 90 in South Dakota, isTranscontinentalRoute, true]
-
A.
mainTranscontinentalConnection
Indicates that something serves as the primary route or link connecting regions or networks that span across an entire continent.
-
B.
locatedInTranscontinentalCountry
Indicates that an entity is situated within a country whose territory spans more than one continent.
-
C.
isOneOfLongestHighwaysIn
Indicates that a highway is among the longest highways within a specified geographic region or jurisdiction.
-
D.
transcontinentalRegion
Indicates a region that spans or extends across more than one continent.
-
E.
crossesContinent
chosen
Indicates that one entity traverses from one side of a continent to the other, passing across its landmass.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6c2930819090bc2b95725fbf18 |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:34 p.m.