Triple
T8554179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Amsterdam |
E202521
|
entity |
| Predicate | historicalUTCOffset |
P1832
|
FINISHED |
| Object | +00:20: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: +00:20:00 | Statement: [Europe/Amsterdam, historicalUTCOffset, +00:20:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalUTCOffset Context triple: [Europe/Amsterdam, historicalUTCOffset, +00:20:00]
-
A.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
B.
timeZoneHistorical
chosen
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
-
C.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
D.
UTCOffsetDaylightSavingTime
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
E.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe8894e7c8190bc0ae2ceec473ecb |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.