Triple
T2525960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mon |
E56034
|
entity |
| Predicate | laterPoliticalStatus |
P13710
|
FINISHED |
| Object | incorporated into Burmese kingdoms |
—
|
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: incorporated into Burmese kingdoms | Statement: [Mon, laterPoliticalStatus, incorporated into Burmese kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPoliticalStatus Context triple: [Mon, laterPoliticalStatus, incorporated into Burmese kingdoms]
-
A.
supportedPoliticalStatus
Indicates that one entity endorsed, favored, or advocated for a particular political status or position of another entity.
-
B.
electoralStatus
Indicates the current state or condition of an entity in relation to an election process (e.g., running, elected, defeated, or not a candidate).
-
C.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
legalStatusAfterCoup
Indicates the legal status or standing of an entity following a coup or unconstitutional change of power.
-
E.
endedPoliticalEntity
Indicates that one political entity brought about the termination or dissolution of another political entity.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2544b4481908e105294cebdbb1f |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.