Triple
T29860143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John of Lusignan |
E758289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of Armenian-Cypriot royalty |
C11665
|
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: member of Armenian-Cypriot royalty Context triple: [John of Lusignan, instanceOf, member of Armenian-Cypriot royalty]
-
A.
Bagratid dynasty member
A Bagratid dynasty member is an individual belonging to the medieval royal family of Armenian and Georgian origin that ruled various Caucasian kingdoms between the 9th and 11th centuries.
-
B.
member of a royal family
chosen
A member of a royal family is an individual related by blood, marriage, or adoption to a reigning or formerly reigning monarch, typically holding a recognized title, status, or role within the monarchy.
-
C.
member of a former royal family
A member of a former royal family is an individual descended from or previously holding status within a monarchy that has since lost its ruling power or official political authority.
-
D.
member of Byzantine imperial family
A member of the Byzantine imperial family is an individual related by blood, marriage, or adoption to the reigning emperor, often holding elevated social status, political influence, and potential claims to the throne within the Byzantine Empire.
-
E.
member of the Trapezuntine imperial family
A member of the Trapezuntine imperial family is an individual belonging by blood or marriage to the ruling Komnenos dynasty of the Empire of Trebizond, holding hereditary status, prestige, and potential claims to imperial authority.
- F. None of above.
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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:48 p.m.