Triple
T30629169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMT |
E779665
|
entity |
| Predicate | isOfficialTimeFor |
P5062
|
FINISHED |
| Object | Myanmar government |
—
|
NE NERFINISHED |
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: Myanmar government | Statement: [MMT, isOfficialTimeFor, Myanmar government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialTimeFor Context triple: [MMT, isOfficialTimeFor, Myanmar government]
-
A.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
B.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
-
C.
isFinalHourOf
Indicates that one time period represents the last hour within the duration or schedule of another time-related entity.
-
D.
usedAsOfficialTime
chosen
Indicates that something is employed as the recognized standard or authoritative reference for measuring time in an official context.
-
E.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
- 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.