Triple
T31676100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A27 motorway (Germany) |
E808401
|
entity |
| Predicate | hasTruckToll |
P178285
|
FINISHED |
| Object | yes, for heavy goods vehicles |
—
|
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, for heavy goods vehicles | Statement: [A27 motorway (Germany), hasTruckToll, yes, for heavy goods vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTruckToll Context triple: [A27 motorway (Germany), hasTruckToll, yes, for heavy goods vehicles]
-
A.
hasTollForTrucks
chosen
Indicates that a toll or fee is required specifically for trucks when using a particular road, route, or facility.
-
B.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
C.
hasTruckTraffic
Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
-
D.
hasTollAgency
Indicates that a transportation facility or route is operated, managed, or overseen by a specific toll-collecting agency.
-
E.
hasTollCollectionRole
Indicates that an entity participates in toll collection with a specified functional role (e.g., operator, collector, or managing authority).
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 30, 2026, 11:03 p.m.