Triple
T9487900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghanistan Time |
E228807
|
entity |
| Predicate | isOffsetBetween |
P74300
|
FINISHED |
| Object | UTC+04:00 and UTC+05:00 |
—
|
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: UTC+04:00 and UTC+05:00 | Statement: [Afghanistan Time, isOffsetBetween, UTC+04:00 and UTC+05:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOffsetBetween Context triple: [Afghanistan Time, isOffsetBetween, UTC+04:00 and UTC+05:00]
-
A.
isOffsetFrom
Indicates that one entity’s position, value, or occurrence is displaced by a specified amount or direction relative to another entity.
-
B.
isIntermediateBetween
chosen
Indicates that one entity occupies a position or state that lies between two other entities in a sequence, range, or process.
-
C.
isAxisBetween
Indicates that one entity serves as a central or reference axis positioned between two other entities in a spatial or structural arrangement.
-
D.
isUnusualOffset
Indicates that one value or position deviates from the expected or standard offset relative to another.
-
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.
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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd80c443b88190968d2092a73e1ee4 |
completed | April 1, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:55 p.m.