Triple
T30749958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinya Kingdom |
E782929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor state of Pagan Empire |
C57209
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: successor state of Pagan Empire Context triple: [Pinya Kingdom, instanceOf, successor state of Pagan Empire]
-
A.
successor state of the Western Roman Empire
A successor state of the Western Roman Empire is a political entity that emerged in its former territories, inheriting and adapting Roman institutions, culture, and legal traditions while developing its own distinct identity.
-
B.
successor state of the Western Roman Empire
A successor state of the Western Roman Empire is a political entity that emerged in former Western Roman territories, inheriting and adapting Roman institutions, culture, and legal traditions while establishing its own distinct governance and identity.
-
C.
Byzantine successor state
A Byzantine successor state is a political entity that emerged from the fragmentation of the Byzantine Empire, claiming continuity with its imperial, cultural, and religious traditions.
-
D.
Crusader state
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
-
E.
Carolingian successor state
A Carolingian successor state is a political entity that emerged from the fragmentation of the Carolingian Empire, inheriting and adapting its territorial, institutional, and cultural legacy in medieval Europe.
- F. None of above. chosen
Provenance (1 batch)
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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:38 p.m.