Triple
T24760271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Highway 121 (Texas) |
E619415
|
entity |
| Predicate | tollSectionOperatedBy |
P134087
|
FINISHED |
| Object | North Texas Tollway Authority |
—
|
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: North Texas Tollway Authority | Statement: [State Highway 121 (Texas), tollSectionOperatedBy, North Texas Tollway Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollSectionOperatedBy Context triple: [State Highway 121 (Texas), tollSectionOperatedBy, North Texas Tollway Authority]
-
A.
tollLanesOperatedBy
Indicates that the specified toll lanes are managed, controlled, or operated by the referenced operator or organization.
-
B.
tollingAuthority
Indicates the entity that has the authority to impose, collect, or manage a toll on a given route, facility, or service.
-
C.
tollSectionState
Indicates the status or condition of a specific toll road section within a tolling system.
-
D.
tollFacilityName
Indicates the name assigned to a toll facility where tolls are collected.
-
E.
hasTollAgency
chosen
Indicates that a transportation facility or route is operated, managed, or overseen by a specific toll-collecting agency.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:27 a.m.