Triple
T38267040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm congestion tax |
E1021091
|
entity |
| Predicate | timeOfDayScope |
P99009
|
FINISHED |
| Object | weekdays only |
—
|
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: weekdays only | Statement: [Stockholm congestion tax, timeOfDayScope, weekdays only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDayScope Context triple: [Stockholm congestion tax, timeOfDayScope, weekdays only]
-
A.
associatedTimeOfDay
Indicates the specific time of day during which an event, state, or relationship occurs or is most relevant.
-
B.
timeOfDayCoverage
chosen
Indicates the specific portion or range of the day during which an activity, service, or condition is in effect or applicable.
-
C.
timeOfWorld
Indicates the specific time or temporal context associated with a particular world or world-state.
-
D.
timeOfDayEmphasized
Indicates that a particular time of day is highlighted or given special prominence in relation to an event or situation.
-
E.
hasTimeOfDay
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:30 p.m.