Triple
T31143198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Ossory |
E793845
|
entity |
| Predicate | heldByDynastyFrom |
P99874
|
FINISHED |
| Object | Mac Giolla Phádraig dynasty |
—
|
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: Mac Giolla Phádraig dynasty | Statement: [Lord of Ossory, heldByDynastyFrom, Mac Giolla Phádraig dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldByDynastyFrom Context triple: [Lord of Ossory, heldByDynastyFrom, Mac Giolla Phádraig dynasty]
-
A.
heldUnderDynasty
chosen
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
B.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
C.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
D.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
E.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.