Triple
T5150766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrestrial Time |
E116186
|
entity |
| Predicate | offsetFromTAI |
P12856
|
FINISHED |
| Object | 32.184 seconds |
—
|
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: 32.184 seconds | Statement: [Terrestrial Time, offsetFromTAI, 32.184 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetFromTAI Context triple: [Terrestrial Time, offsetFromTAI, 32.184 seconds]
-
A.
differenceFromTAI
chosen
Indicates the degree or nature of deviation between something and a reference point defined as TAI (e.g., a target, standard, or baseline associated with TAI).
-
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.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
D.
offsetFromJapanStandardTime
Indicates the time difference between a given time zone or time value and Japan Standard Time (JST), typically expressed as an offset in hours or minutes.
-
E.
offsetFrom
Indicates that one entity is positioned or scheduled at a specific distance, time, or value away from another reference entity.
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.