Triple
T21415407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss motorway vignette |
E528287
|
entity |
| Predicate | penaltyForMissingVignette |
P143879
|
FINISHED |
| Object | on-the-spot fine |
—
|
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: on-the-spot fine | Statement: [Swiss motorway vignette, penaltyForMissingVignette, on-the-spot fine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyForMissingVignette Context triple: [Swiss motorway vignette, penaltyForMissingVignette, on-the-spot fine]
-
A.
penaltyForMissingGate
Indicates a penalty that is applied when a required gate, checkpoint, or stage is missed.
-
B.
penaltyAppliesTo
Indicates that a specific penalty is imposed on, or is relevant to, a particular entity or situation.
-
C.
penaltyPoints
Indicates that a certain number of negative points or demerits are assigned to an entity as a consequence of a rule violation, error, or infraction.
-
D.
tollExemption
Indicates that an entity is not required to pay a toll or fee that would normally be charged for using a particular route, facility, or service.
-
E.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
- 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.