Triple
T30698159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway Loop 1 |
E781532
|
entity |
| Predicate | tollLanesType |
P159215
|
FINISHED |
| Object | express lanes |
—
|
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: express lanes | Statement: [Texas State Highway Loop 1, tollLanesType, express lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tollLanesType Context triple: [Texas State Highway Loop 1, tollLanesType, express lanes]
-
A.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
B.
tollLanesOperatedBy
Indicates that the specified toll lanes are managed, controlled, or operated by the referenced operator or organization.
-
C.
tollRoadOf
Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
-
D.
tollRoadClass
chosen
Indicates the classification or category assigned to a toll road based on its type, characteristics, or tolling scheme.
-
E.
typicalLanes
Indicates the usual or standard number or configuration of lanes associated with a road or similar transportation segment.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68bdceb8c8190b78e499ea2357e0f |
completed | May 2, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:34 p.m.