Triple
T10371038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayeyarwady Region |
E244382
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Pyapon |
E860735
|
NE 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: Pyapon | Statement: [Ayeyarwady Region, contains, Pyapon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyapon Context triple: [Ayeyarwady Region, contains, Pyapon]
-
A.
Pyapon District
chosen
Pyapon District is an administrative district in Myanmar known for its deltaic landscape and rice-growing communities within the Ayeyarwady Region.
-
B.
Arakan
Arakan is a historical coastal region in western Myanmar, now largely corresponding to Rakhine State and known for its distinct ethnic and cultural identity.
-
C.
Thayarwady
Thayarwady is a town in central Myanmar known as an administrative and commercial center within the Bago Region.
-
D.
Magway
Magway is a city in central Myanmar situated on the Irrawaddy River, known as an administrative, commercial, and agricultural hub of the surrounding region.
-
E.
Ta’ang
Ta’ang is a Mon–Khmer language spoken primarily by the Ta’ang (Palaung) ethnic group in parts of Myanmar and neighboring regions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9737cfc81909d6302bd4177d186 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fb8e96e081908282bb0f82719abe |
completed | April 9, 2026, 7:18 p.m. |
Created at: April 6, 2026, 12:01 p.m.