Triple

T16988232
Position Surface form Disambiguated ID Type / Status
Subject Autobahn A2 E412124 entity
Predicate hasTollFor P27349 FINISHED
Object 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: heavy goods vehicles | Statement: [Autobahn A2, hasTollFor, heavy goods vehicles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTollFor
Context triple: [Autobahn A2, hasTollFor, heavy goods vehicles]
  • A. hasToll
    Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
  • B. hasTollSegment
    Indicates that a route, road, or path includes a segment where a toll must be paid.
  • C. appliesTollTo chosen
    Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
  • D. hasTollVariant
    Indicates that an entity has a version or instance that requires paying a toll or fee for use or access.
  • E. isTollRoadDestination
    Indicates that a location serves as a destination reachable via a toll road or requiring travel on a toll road to access it.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d27cd2048190800a60ae653e11e1 completed April 18, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69e35d4dff4881909b384e30f2d36bff completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:32 a.m.