Triple
T4046742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss motorway network |
E84083
|
entity |
| Predicate | vignetteValidityPeriod |
P33304
|
FINISHED |
| Object | one calendar year |
—
|
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: one calendar year | Statement: [Swiss motorway network, vignetteValidityPeriod, one calendar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vignetteValidityPeriod Context triple: [Swiss motorway network, vignetteValidityPeriod, one calendar year]
-
A.
hasValidityPeriod
chosen
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
B.
validityPeriodForAdults
Indicates the time span during which something is considered valid or applicable specifically for adults.
-
C.
validityType
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
D.
hasValidityPeriodPersonalCard
Indicates that a personal card is associated with a specific time period during which it is valid or in effect.
-
E.
ticketValidityCovers
Indicates that the validity period or scope of a ticket extends to and includes a specified time, location, service, or condition.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb62593c8190ab8462c4d9cd9d08 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.