Triple
T36984647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri state transportation system |
E914928
|
entity |
| Predicate | majorInterstate |
P86751
|
FINISHED |
| Object | Interstate 70 |
—
|
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: Interstate 70 | Statement: [Missouri state transportation system, majorInterstate, Interstate 70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorInterstate Context triple: [Missouri state transportation system, majorInterstate, Interstate 70]
-
A.
primaryInterstateHighway
chosen
Indicates that the subject is designated as a primary (main) interstate highway within the interstate highway system.
-
B.
hasInterstate
Indicates that there exists an interstate connection or highway link between the related entities.
-
C.
interstateFunction
Indicates a functional relationship or interaction that occurs between or involves multiple states or state-level systems.
-
D.
majorState
Indicates that a state holds significant power, influence, or importance relative to other states within a given system or context.
-
E.
isAuxiliaryInterstate
Indicates that one roadway functions as an auxiliary route (such as a spur, loop, or bypass) of a primary Interstate highway.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe23081408190a121d901dbce1403 |
completed | May 10, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ffe18aed348190912a5996b2da728b |
completed | May 10, 2026, 1:38 a.m. |
Created at: May 3, 2026, 4:14 p.m.