Triple
T35677684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enso |
E1030908
|
entity |
| Predicate | timeZoneBeforeCession |
P184070
|
FINISHED |
| Object | Eastern European Time |
—
|
NE NERFINISHED |
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: Eastern European Time | Statement: [Enso, timeZoneBeforeCession, Eastern European Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneBeforeCession Context triple: [Enso, timeZoneBeforeCession, Eastern European Time]
-
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.
timeZoneOnUSSide
Indicates that the referenced time zone is the one used on the United States side of a border, region, or cross-national context.
-
C.
timeZoneState
Indicates that one entity is a state or region associated with the time zone of another entity.
-
D.
timeZoneSide1
Indicates that the first entity is associated with or located in a particular time zone.
-
E.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
- F. None of above. chosen
Provenance (4 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.