Triple
T32306140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahlaing Township |
E825374
|
entity |
| Predicate | hasPrimaryTimeZoneCountry |
P202795
|
FINISHED |
| Object | Myanmar Standard Time |
—
|
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 Standard Time | Statement: [Mahlaing Township, hasPrimaryTimeZoneCountry, Myanmar Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTimeZoneCountry Context triple: [Mahlaing Township, hasPrimaryTimeZoneCountry, Myanmar Standard Time]
-
A.
hasPrimaryCountryCode
Indicates that an entity is associated with its main or officially designated country code.
-
B.
hasAlternativeTimeZoneInCountry
Indicates that an entity has a different or additional time zone specifically applicable within a given country.
-
C.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
D.
isSingleTimeZoneForCountry
Indicates that a country uses a single, uniform time zone throughout its entire territory.
-
E.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_6a00bc06bf3081908973b6c05797299f |
completed | May 10, 2026, 5:10 p.m. |
Created at: May 1, 2026, 12:45 a.m.