Triple
T1423473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRT |
E30277
|
entity |
| Predicate | offsetFromUTCInSeconds |
P4887
|
FINISHED |
| Object | 10800 |
—
|
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: 10800 | Statement: [TRT, offsetFromUTCInSeconds, 10800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetFromUTCInSeconds Context triple: [TRT, offsetFromUTCInSeconds, 10800]
-
A.
offsetInSecondsFromUTC
chosen
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
B.
offsetFromUTC
Indicates the time difference between a given time value and Coordinated Universal Time (UTC), typically expressed as an offset in hours and/or minutes.
-
C.
offsetFromUTCInMinutes
Indicates the number of minutes by which a given time value differs from Coordinated Universal Time (UTC), positive or negative.
-
D.
offsetFromUTCInHours
Indicates the number of hours a time value is offset from Coordinated Universal Time (UTC), positive for time zones ahead and negative for those behind.
-
E.
offsetFromEasternEuropeanTime
Indicates that one time value is a specified offset relative to Eastern European Time (EET).
- 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.