Triple
T6770273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Thruway Authority |
E155024
|
entity |
| Predicate | typeOfTollSystem |
P73181
|
FINISHED |
| Object | toll road operator |
—
|
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: toll road operator | Statement: [New York State Thruway Authority, typeOfTollSystem, toll road operator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTollSystem Context triple: [New York State Thruway Authority, typeOfTollSystem, toll road operator]
-
A.
tollingType
Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
-
B.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
C.
isTollFacilityOf
Indicates that a facility (such as a toll booth, plaza, or gantry) is part of, or used to collect tolls for, a specific toll road or toll transportation infrastructure.
-
D.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
E.
electronicTollBrand
Indicates that an entity is associated with or accepts a particular brand of electronic toll collection system.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2347fb48190a44c03317b5ecfd7 |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:13 p.m.