Triple
T27214121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick of Montferrat |
E684088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Aleramici dynasty |
C52616
|
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 the Aleramici dynasty Context triple: [Frederick of Montferrat, instanceOf, member of the Aleramici dynasty]
-
A.
member of the Visconti dynasty
A member of the Visconti dynasty is an individual belonging to the powerful medieval and Renaissance noble family that ruled Milan and surrounding territories in northern Italy.
-
B.
Conradine dynasty member
A Conradine dynasty member is an individual belonging to the early medieval German noble family that held significant power in Franconia and briefly provided a king of East Francia in the 10th century.
-
C.
member of the House of Este
A member of the House of Este is an individual belonging to the historic Italian noble dynasty that ruled territories such as Ferrara, Modena, and Reggio and played a significant role in European politics and culture from the Middle Ages onward.
-
D.
member of the Gattilusio family
A member of the Gattilusio family is an individual belonging to the medieval Genoese noble lineage that ruled several Aegean islands and coastal territories under Byzantine and later Ottoman influence.
-
E.
member of the Conti di Segni family
A member of the Conti di Segni family is an individual belonging to the medieval Italian noble lineage from Segni, noted for producing influential churchmen, including several popes and cardinals.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:40 a.m.