Triple
T7946957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BJT |
E184520
|
entity |
| Predicate | timeRelationToGMT |
P26622
|
FINISHED |
| Object | 8 hours ahead of GMT |
—
|
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: 8 hours ahead of GMT | Statement: [BJT, timeRelationToGMT, 8 hours ahead of GMT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeRelationToGMT Context triple: [BJT, timeRelationToGMT, 8 hours ahead of GMT]
-
A.
timeDifferenceWithGreenwichMeanTime
chosen
Indicates the time offset or difference between a given time reference and Greenwich Mean Time (GMT).
-
B.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
C.
relationToUTC
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
D.
timeOffsetReference
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
-
E.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.