Triple
T21415418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss motorway vignette |
E528287
|
entity |
| Predicate | electronicVignetteLinkedTo |
P97049
|
FINISHED |
| Object | vehicle licence plate |
—
|
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: vehicle licence plate | Statement: [Swiss motorway vignette, electronicVignetteLinkedTo, vehicle licence plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electronicVignetteLinkedTo Context triple: [Swiss motorway vignette, electronicVignetteLinkedTo, vehicle licence plate]
-
A.
supportsElectronicTollCollection
chosen
Indicates that an entity is capable of handling or is compatible with electronic toll collection systems for automated toll payment.
-
B.
electronicTollBrand
Indicates that an entity is associated with or accepts a particular brand of electronic toll collection system.
-
C.
hasElectronicTicketing
Indicates that an entity supports or provides electronic ticketing for access, booking, or transactions.
-
D.
fareSystem
Indicates a relationship where a system is used to determine, collect, or manage fares or payments for transportation or similar services.
-
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.
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_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. |
Created at: April 16, 2026, 5:45 p.m.