Triple
T30804431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyck |
E784458
|
entity |
| Predicate | timezonePresentDayLocation |
P103459
|
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: [Lyck, timezonePresentDayLocation, Central European Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezonePresentDayLocation Context triple: [Lyck, timezonePresentDayLocation, Central European Time]
-
A.
timezoneTodayOfCityItRefersTo
Indicates that the referenced entity’s current date or “today” is determined according to the time zone of the specified city.
-
B.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
C.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
-
D.
timeZoneCity
chosen
Indicates that a city is located within or associated with a particular time zone.
-
E.
timeInRegion
Indicates that a specified amount of time is spent, occurs, or is measured within a particular geographic or defined region.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:42 p.m.