Triple
T5150768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrestrial Time |
E116186
|
entity |
| Predicate | epochOffsetValue |
P4821
|
FINISHED |
| Object | TT = TAI + 32.184 s |
—
|
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: TT = TAI + 32.184 s | Statement: [Terrestrial Time, epochOffsetValue, TT = TAI + 32.184 s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epochOffsetValue Context triple: [Terrestrial Time, epochOffsetValue, TT = TAI + 32.184 s]
-
A.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
B.
offsetSeconds
chosen
Indicates a temporal relationship where one event or time point occurs a specified number of seconds before or after another reference time.
-
C.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference 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.
epochOfKeyObservations
Indicates the specific time period during which the key or defining observations relevant to something were made.
- 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.