Triple
T6141294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clifton Suspension Bridge |
E136966
|
entity |
| Predicate | hasTollBooths |
P36751
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Clifton Suspension Bridge, hasTollBooths, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTollBooths Context triple: [Clifton Suspension Bridge, hasTollBooths, yes]
-
A.
hasTollBoothsAt
chosen
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
B.
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.
-
C.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
D.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
E.
hasHighOccupancyTollLanes
Indicates that a roadway or highway segment includes high-occupancy toll (HOT) lanes where vehicles meeting certain occupancy or payment conditions are allowed to travel.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb2404c8190bbbfa78d5f49389f |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.