Triple
T38296754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Africa/Cairo |
E1032108
|
entity |
| Predicate | timeZoneNameStandard |
P6292
|
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: [Africa/Cairo, timeZoneNameStandard, Eastern European Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneNameStandard Context triple: [Africa/Cairo, timeZoneNameStandard, Eastern European Time]
-
A.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
B.
standardTimeName
chosen
Indicates the official name assigned to a particular standard time used in a region or context.
-
C.
timeZoneDesignation
Indicates the specific time zone label or code assigned to an entity for representing its local time.
-
D.
countryTimeStandardFor
Indicates that a specific time standard (such as a time zone or time-keeping system) is officially used by a given country.
-
E.
UTCOffsetStandardTime
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.