Triple
T32369380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Königsberg (Braunfels) |
E827089
|
entity |
| Predicate | hasTimeOffsetUTC_DST |
P713
|
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: [Königsberg (Braunfels), hasTimeOffsetUTC_DST, +02:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOffsetUTC_DST Context triple: [Königsberg (Braunfels), hasTimeOffsetUTC_DST, +02:00]
-
A.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
-
B.
hasStandardTimeUTCOffset
Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
-
C.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
D.
UTCOffsetDaylightSavingTime
chosen
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
E.
observesDSTOffset
Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 12:50 a.m.