Triple
T32362235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cibalae |
E826894
|
entity |
| Predicate | timeZoneModernLocation |
P11952
|
FINISHED |
| Object | Central 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: Central European Time | Statement: [Cibalae, timeZoneModernLocation, Central European Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneModernLocation Context triple: [Cibalae, timeZoneModernLocation, Central European Time]
-
A.
timeZoneCity
Indicates that a city is located within or associated with a particular time zone.
-
B.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
C.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
D.
timeZoneEndpoint
Indicates a connection or boundary point where a specific time zone applies or is defined.
-
E.
timeZoneName
chosen
Indicates the specific time zone designation (such as its standard name or label) associated with an 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:49 a.m.