Triple
T33037239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eóganacht Glendamnach |
E845350
|
entity |
| Predicate | sharesDynasticSystemWith |
P15924
|
FINISHED |
| Object | Eóganacht Chaisil |
—
|
NE NERFINISHED |
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: Eóganacht Chaisil | Statement: [Eóganacht Glendamnach, sharesDynasticSystemWith, Eóganacht Chaisil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDynasticSystemWith Context triple: [Eóganacht Glendamnach, sharesDynasticSystemWith, Eóganacht Chaisil]
-
A.
sharesDynasticOrderWith
chosen
Indicates that two entities belong to or are associated with the same dynastic sequence or ruling lineage.
-
B.
dynasticStructure
Indicates the hierarchical organization and succession relationships within a dynasty or ruling family.
-
C.
dynasticInheritance
Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
-
D.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
-
E.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff956dc6548190979171d4b4068d47 |
completed | May 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69ff93dc39c481908a97a12c3ef7dfe7 |
completed | May 9, 2026, 8:06 p.m. |
Created at: May 1, 2026, 1:24 a.m.