Triple
T34531150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFT |
E886538
|
entity |
| Predicate | timeStandardRelativeToUTC |
P712
|
FINISHED |
| Object | UTC+11 |
—
|
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+11 | Statement: [NFT, timeStandardRelativeToUTC, UTC+11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStandardRelativeToUTC Context triple: [NFT, timeStandardRelativeToUTC, UTC+11]
-
A.
utcTime
Indicates that the associated time value is expressed in Coordinated Universal Time (UTC), independent of local time zones.
-
B.
relationToUTC
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
C.
UTCOffsetStandardTime
chosen
Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
-
D.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
E.
timeDifferenceFromCentralStandard
Indicates the time offset between a given time reference and Central Standard Time (CST), typically expressed as the difference in hours or minutes.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fbfe61c81909bcfd3ba504769e7 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.