Triple
T20789990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Vienna |
E511746
|
entity |
| Predicate | standardTimeSeason |
P87188
|
FINISHED |
| Object | winter |
—
|
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: winter | Statement: [Europe/Vienna, standardTimeSeason, winter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTimeSeason Context triple: [Europe/Vienna, standardTimeSeason, winter]
-
A.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
B.
standardTimeAllYear
Indicates that a location or entity observes standard time throughout the entire year without switching to daylight saving time.
-
C.
standardTimeName
Indicates the official name assigned to a particular standard time used in a region or context.
-
D.
standardTimeDesignation
Indicates that one entity designates or specifies the standard (non-daylight-saving) time applicable to another entity.
-
E.
isSeasonalStandard
chosen
Indicates that something follows or conforms to the standard conditions, rules, or patterns that apply only during a specific season or time period.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28f0e1081909f18dddfc6ec084c |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.