Triple
T24344853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas–Fort Worth vs. Houston |
E613610
|
entity |
| Predicate | isIntrastate |
P155796
|
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: [Dallas–Fort Worth vs. Houston, isIntrastate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIntrastate Context triple: [Dallas–Fort Worth vs. Houston, isIntrastate, true]
-
A.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
B.
hasInterstate
Indicates that there exists an interstate connection or highway link between the related entities.
-
C.
isLocalOptionTax
Indicates that a tax is imposed at a local (e.g., city or county) level as an optional levy rather than as a mandatory statewide or national tax.
-
D.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
E.
isInLandlockedPartOfState
Indicates that a location lies within the portion of a state that has no direct access to the sea or ocean.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29328b0288190a580939e8863b0c2 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:58 a.m.