Triple
T30629175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMT |
E779665
|
entity |
| Predicate | offsetFromPST |
P170774
|
FINISHED |
| Object | +14:30 |
—
|
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: +14:30 | Statement: [MMT, offsetFromPST, +14:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetFromPST Context triple: [MMT, offsetFromPST, +14:30]
-
A.
offsetFromAlaskaStandardTime
Indicates the time difference between a given time value and Alaska Standard Time (AST), typically expressed as an offset in hours or minutes.
-
B.
offsetFromAtlanticStandardTime
Indicates the time difference, in hours or minutes, between a given time reference and Atlantic Standard Time.
-
C.
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.
-
D.
offsetFromHawaiiStandardTime
Indicates the time difference between a given time value and Hawaii Standard Time (HST), typically expressed as an offset in hours or minutes.
-
E.
offsetFromStandardTime
Indicates the time difference between a given local time and the corresponding standard time for that location.
- F. None of above. chosen
Provenance (4 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:28 p.m.