Triple
T32879244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asanina |
E841010
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine aristocratic lineage |
C60438
|
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: Byzantine aristocratic lineage Context triple: [Asanina, instanceOf, Byzantine aristocratic lineage]
-
A.
Basque noble lineage
A Basque noble lineage is a hereditary aristocratic family originating from the Basque Country, defined by shared ancestry, territorial ties, and enduring social prestige within regional historical and political structures.
-
B.
medieval Roman noble family
A medieval Roman noble family is an aristocratic lineage based in Rome during the Middle Ages, wielding political, economic, and social influence through landholdings, alliances, and roles in civic and ecclesiastical institutions.
-
C.
Greek aristocrat
A Greek aristocrat is a wealthy, high-status individual from ancient or modern Greece, typically belonging to a privileged landowning or politically influential family and embodying traditional cultural refinement and social power.
-
D.
Peruvian noble lineage
A Peruvian noble lineage is a hereditary social class in Peru composed of families that trace their prestige, titles, and status to pre-Columbian indigenous nobility, colonial-era aristocracy, or recognized republican-era elites.
-
E.
Gallo-Roman aristocrat
A Gallo-Roman aristocrat is a wealthy, landowning elite of Romanized Gaul who blended Roman political, cultural, and social practices with local Gallic traditions to maintain regional power and influence.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:18 a.m.