Triple
T1184963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukon Time Zone |
E25223
|
entity |
| Predicate | offsetType |
P25007
|
FINISHED |
| Object | fixed UTC offset |
—
|
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: fixed UTC offset | Statement: [Yukon Time Zone, offsetType, fixed UTC offset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetType Context triple: [Yukon Time Zone, offsetType, fixed UTC offset]
-
A.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
B.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
C.
deltaType
Indicates a classification of the kind or category of change (difference) that has occurred between two related states or versions.
-
D.
oreType
Indicates the specific kind or classification of ore associated with an entity.
-
E.
usesOffsetFrom
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
- F. None of above. chosen
Provenance (4 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd39245881908766c41943dc2752 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc6d5b7881908091e40c8695ef53 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:45 p.m.