Triple
T31938338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Childress, Texas vicinity |
E815454
|
entity |
| Predicate | primaryStateHighwayAccess |
P12245
|
FINISHED |
| Object | Texas State Highway 6 |
E151878
|
NE 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: Texas State Highway 6 | Statement: [Childress, Texas vicinity, primaryStateHighwayAccess, Texas State Highway 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStateHighwayAccess Context triple: [Childress, Texas vicinity, primaryStateHighwayAccess, Texas State Highway 6]
-
A.
isPrimaryStateHighway
Indicates that a given road segment is designated as a primary (major) state highway within a state’s road network.
-
B.
primaryHighwayComponent
Indicates that one entity serves as the main or principal highway component associated with another entity.
-
C.
primaryInterstateHighway
Indicates that the subject is designated as a primary (main) interstate highway within the interstate highway system.
-
D.
isOnlyMajorRoadAccessTo
Indicates that one road is the sole major roadway providing access to a particular place or area.
-
E.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
- F. None of above.
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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389bf2d60c8190937c8cb5940a003a |
completed | June 22, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:05 a.m.