Triple
T30629163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMT |
E779665
|
entity |
| Predicate | changeToCurrentOffsetApproxYear |
P151453
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [MMT, changeToCurrentOffsetApproxYear, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeToCurrentOffsetApproxYear Context triple: [MMT, changeToCurrentOffsetApproxYear, 1945]
-
A.
movedToCurrentDateYear
Indicates that an entity has been moved, updated, or adjusted so that its associated date now falls within the current calendar year.
-
B.
approximateSettingYear
Indicates the approximate calendar year in which the primary events or setting of something (e.g., a work or scenario) take place.
-
C.
historicalUtcOffsetChangeYear
chosen
Indicates the year in which the UTC offset for a given entity (such as a time zone or region) changed from its previous value.
-
D.
movedToCurrentDateBy
Indicates that something has been rescheduled, adjusted, or shifted so that it now occurs or is set on the current date by a particular agent or process.
-
E.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1c41ec81909d892e7f364f1c5b |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:28 p.m.