Triple
T35291109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felsberg |
E1019227
|
entity |
| Predicate | likelyTimeZone |
P109
|
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: [Felsberg, likelyTimeZone, Central European Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyTimeZone Context triple: [Felsberg, likelyTimeZone, Central European Time]
-
A.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
-
B.
locatedInTimeZone
chosen
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
C.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
D.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
-
E.
timeZoneImplication
Indicates that one time zone condition or setting logically leads to, constrains, or determines another time zone condition or setting.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.