Triple
T30894443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thado Minbya |
E786984
|
entity |
| Predicate | consolidatedRegion |
P170277
|
FINISHED |
| Object | central Burma |
—
|
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: central Burma | Statement: [Thado Minbya, consolidatedRegion, central Burma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidatedRegion Context triple: [Thado Minbya, consolidatedRegion, central Burma]
-
A.
reorganisedRegion
Indicates that a region has undergone a structural or administrative change, resulting in a new or altered regional configuration.
-
B.
consolidatedUnder
Indicates that one entity has been merged into and is now formally part of another, typically larger or parent, entity.
-
C.
consolidatedAs
Indicates that one entity has been combined, merged, or unified into another entity to form a single consolidated whole.
-
D.
convertedRegion
Indicates that one region has been transformed, adapted, or changed into another region or regional form.
-
E.
isConsolidatedDistrict
Indicates that a district has been formed by combining two or more previously separate districts into a single administrative or organizational unit.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923a69048190ba22deee04c20e30 |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:49 p.m.