Triple
T31719652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toirdelbach Ua Briain |
E809537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ua Briain dynasty member |
C10357
|
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: Ua Briain dynasty member Context triple: [Toirdelbach Ua Briain, instanceOf, Ua Briain dynasty member]
-
A.
member of the O'Brien dynasty
chosen
A member of the O'Brien dynasty is an individual descended from or affiliated with the historic Irish royal lineage traditionally traced to Brian Boru, High King of Ireland.
-
B.
member of the FitzGerald dynasty
A member of the FitzGerald dynasty is an individual belonging to the historically influential Anglo-Norman noble family that held significant political, military, and social power in Ireland and Britain from the medieval period onward.
-
C.
member of the O'Rourke dynasty
A member of the O'Rourke dynasty is an individual belonging to a historically influential Irish noble lineage known for its regional leadership, political power, and cultural legacy.
-
D.
Ottonian dynasty member
An Ottonian dynasty member is an individual belonging to the German royal and imperial family that ruled the East Frankish (German) kingdom and Holy Roman Empire from the early 10th to early 11th centuries, beginning with Henry the Fowler and most prominently represented by Otto I, Otto II, and Otto III.
-
E.
member of the de Burgh family
A member of the de Burgh family is an individual belonging to the historically significant Anglo-Norman noble lineage known for its political influence and landholdings in medieval Ireland and England.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:18 p.m.