Triple
T24684995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Paris |
E611256
|
entity |
| Predicate | typicalSummerOffsetFromUTC |
P47604
|
FINISHED |
| Object | +02:00 |
—
|
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: +02:00 | Statement: [Europe/Paris, typicalSummerOffsetFromUTC, +02:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSummerOffsetFromUTC Context triple: [Europe/Paris, typicalSummerOffsetFromUTC, +02:00]
-
A.
summerUtcOffset
chosen
Indicates the difference in hours or minutes between local time and Coordinated Universal Time (UTC) during the summer or daylight saving period.
-
B.
summerTimeZone
Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
-
C.
typicalOffsetWinter
Indicates the usual temporal or spatial offset associated with winter in relation to a reference point or period.
-
D.
typicalOffsetFromCentralTime
Indicates the usual time difference between a given time zone and Central Time (CT), expressed as an offset in hours or minutes.
-
E.
typicalUtcOffsetRange
Indicates the usual range of UTC time offsets during which an entity (such as a place or time zone) normally operates, accounting for standard and daylight saving variations.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 3:17 a.m.