Triple
T28020123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federal highway network |
E707661
|
entity |
| Predicate | truckTollSystem |
P73181
|
FINISHED |
| Object | Lkw-Maut in Germany |
—
|
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: Lkw-Maut in Germany | Statement: [German federal highway network, truckTollSystem, Lkw-Maut in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: truckTollSystem Context triple: [German federal highway network, truckTollSystem, Lkw-Maut in Germany]
-
A.
operatesTollSystem
Indicates that an entity is responsible for running and managing a toll collection system.
-
B.
typeOfTollSystem
chosen
Indicates the specific kind or category of toll collection system used in a given context.
-
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
Indicates the classification or category assigned to a toll road based on its type, characteristics, or tolling scheme.
-
E.
tollRoadFunction
Indicates that a road segment operates as a toll facility, requiring payment from users for access or passage.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c0a2d208190b8a611be07ac5977 |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:09 p.m.