Triple
T30584403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingalar Taung Nyunt Township |
E778465
|
entity |
| Predicate | isCentralTownshipOf |
P41403
|
FINISHED |
| Object | Yangon |
—
|
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: Yangon | Statement: [Mingalar Taung Nyunt Township, isCentralTownshipOf, Yangon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralTownshipOf Context triple: [Mingalar Taung Nyunt Township, isCentralTownshipOf, Yangon]
-
A.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
B.
isCentralLocalityOf
chosen
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
C.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
-
D.
isRuralMunicipalityOf
Indicates that one entity is a rural municipality that is administratively or geographically part of, or governed by, another entity.
-
E.
hasCentralCounty
Indicates that an administrative or geographic region is associated with a specific county that serves as its central or primary county.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:23 p.m.