Triple
T20606508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 69E in Texas |
E506324
|
entity |
| Predicate | signedAsInterstate |
P140738
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Interstate 69E in Texas, signedAsInterstate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedAsInterstate Context triple: [Interstate 69E in Texas, signedAsInterstate, yes]
-
A.
hasInterstate
Indicates that there exists an interstate connection or highway link between the related entities.
-
B.
connectsToInterstate
Indicates that one roadway, route, or location has a direct connection or access point to an interstate highway.
-
C.
isAuxiliaryInterstateOf
Indicates that one interstate highway functions as an auxiliary route (such as a spur, loop, or bypass) of another primary interstate highway.
-
D.
openedAsInterstateDesignation
Indicates that a roadway or route first began operation under an official interstate highway designation.
-
E.
interstateFunction
Indicates a functional relationship or interaction that occurs between or involves multiple states or state-level systems.
- F. None of above. chosen
Provenance (4 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad394e8819080185187a8b3de93 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a9f3f88190b961db9aca36f7da |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:41 a.m.