Triple
T28277742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burke family |
E713049
|
entity |
| Predicate | hereditaryLeadership |
P31750
|
FINISHED |
| Object | chieftains of Burke septs in Connacht |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: chieftains of Burke septs in Connacht | Statement: [Burke family, hereditaryLeadership, chieftains of Burke septs in Connacht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryLeadership Context triple: [Burke family, hereditaryLeadership, chieftains of Burke septs in Connacht]
-
A.
leadershipDynasty
Indicates a succession relationship where leadership is passed down within the same family or ruling line over time.
-
B.
heritageSuccessor
Indicates that one entity is the successor or inheritor of another in terms of heritage, lineage, or cultural tradition.
-
C.
successionInfluence
Indicates that one entity affects, shapes, or determines the succession or inheritance of another entity.
-
D.
hasHereditaryChief
chosen
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
E.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
- F. None of above.
Provenance (3 batches)
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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6444d26948190a5d87f6b105c86cf |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:20 p.m.