Triple
T32373179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamethin Township |
E827201
|
entity |
| Predicate | hasOfficialTimeZone |
P132463
|
FINISHED |
| Object | MMT |
—
|
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: MMT | Statement: [Yamethin Township, hasOfficialTimeZone, MMT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialTimeZone Context triple: [Yamethin Township, hasOfficialTimeZone, MMT]
-
A.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
B.
hasStandardTimeZone
chosen
Indicates that an entity is associated with a particular standard time zone used to define its official local time.
-
C.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
-
D.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
E.
hasTimeZoneInWinter
Indicates that an entity is associated with a specific time zone during the winter season.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:50 a.m.