Triple
T4116257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Berlin |
E90298
|
entity |
| Predicate | summerTimeZoneOffset |
P47604
|
FINISHED |
| Object | +2 |
—
|
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: +2 | Statement: [State of Berlin, summerTimeZoneOffset, +2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerTimeZoneOffset Context triple: [State of Berlin, summerTimeZoneOffset, +2]
-
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.
differenceFromLondonTimeInSummer
Indicates the time difference between a given location and London during the summer (daylight saving) period.
-
D.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
E.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.