Triple
T1789196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagratid Armenia |
E39456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Armenian kingdom |
C8478
|
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: medieval Armenian kingdom Context triple: [Bagratid Armenia, instanceOf, medieval Armenian kingdom]
-
A.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
B.
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.
-
C.
institution of the Kingdom of Hungary
An institution of the Kingdom of Hungary is an organized body or establishment—political, legal, religious, educational, or administrative—that operated within and under the authority of the historical Kingdom of Hungary.
-
D.
maritime kingdom
A maritime kingdom is a sovereign state whose power, economy, and culture are primarily based on seafaring, naval strength, and control of important sea routes and coastal territories.
-
E.
late medieval ruler
A late medieval ruler is a sovereign who governed a kingdom or principality in Europe roughly between the 13th and 15th centuries, navigating feudal structures, emerging centralized authority, and complex dynastic, religious, and military conflicts.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.