Triple
T28020122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federal highway network |
E707661
|
entity |
| Predicate | hasTollForTrucks |
P178285
|
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: [German federal highway network, hasTollForTrucks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTollForTrucks Context triple: [German federal highway network, hasTollForTrucks, yes]
-
A.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
B.
hasTollBoothsAt
Indicates that toll booths are present at or associated with a particular location or segment of infrastructure.
-
C.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
D.
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.
-
E.
hasTollVariant
Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 27, 2026, 8:09 p.m.