Triple
T1423464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRT |
E30277
|
entity |
| Predicate | previousDSTTimeInTurkey |
P5577
|
FINISHED |
| Object | EEST |
—
|
LITERAL FINISHED |
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: EEST | Statement: [TRT, previousDSTTimeInTurkey, EEST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousDSTTimeInTurkey Context triple: [TRT, previousDSTTimeInTurkey, EEST]
-
A.
previousUTCOffset
chosen
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
B.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
D.
DSTTimeZone
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
-
E.
DSTChangeYear
Indicates the specific year in which a daylight saving time (DST) change occurs or is scheduled to occur.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.