Triple
T17080672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pripyat |
E414459
|
entity |
| Predicate | timeZoneBeforeEvacuation |
P26707
|
FINISHED |
| Object | UTC+3 |
—
|
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: UTC+3 | Statement: [Pripyat, timeZoneBeforeEvacuation, UTC+3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneBeforeEvacuation Context triple: [Pripyat, timeZoneBeforeEvacuation, UTC+3]
-
A.
timeZoneChange
Indicates a change in the time zone associated with an entity, such as shifting from one time offset or region-based time standard to another.
-
B.
timeZoneDestination
Indicates the time zone associated with the destination location in a given context or event.
-
C.
timeZoneState
Indicates that one entity is a state or region associated with the time zone of another entity.
-
D.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
E.
timeZoneContext
chosen
Indicates the time zone setting or context in which an event, action, or relationship is interpreted.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.