Triple

T21415417
Position Surface form Disambiguated ID Type / Status
Subject Swiss motorway vignette E528287 entity
Predicate electronicVignetteIntroduced P143880 FINISHED
Object 2023 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: 2023 | Statement: [Swiss motorway vignette, electronicVignetteIntroduced, 2023]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: electronicVignetteIntroduced
Context triple: [Swiss motorway vignette, electronicVignetteIntroduced, 2023]
  • A. supportsElectronicTollCollection
    Indicates that an entity is capable of handling or is compatible with electronic toll collection systems for automated toll payment.
  • B. hasElectronicTicketing
    Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
  • C. tollIntroduced
    Indicates that a toll was established or put into effect for using a particular route, facility, or service.
  • D. hasFareControlIntegrationSince
    Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
  • E. EVAType
    Indicates the type or category of an extravehicular activity (EVA) associated with an entity, specifying what kind of EVA operation or event it represents.
  • 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_69e0c454c248819093425d1099101c09 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee62d16bfc8190a1c08dd9d0c80e02 completed April 26, 2026, 7:09 p.m.
PD Predicate disambiguation batch_69e61633f8208190a2a849457c4e4198 completed April 20, 2026, 12:04 p.m.
PDg Predicate description generation batch_69e6190163448190a2404b396215c686 completed April 20, 2026, 12:16 p.m.
Created at: April 16, 2026, 5:45 p.m.