Triple
T31142487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Ossory |
E793826
|
entity |
| Predicate | rulingFamilySurname |
P87901
|
FINISHED |
| Object | Mac Giolla Phádraig |
—
|
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 | Statement: [Kingdom of Ossory, rulingFamilySurname, Mac Giolla Phádraig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingFamilySurname Context triple: [Kingdom of Ossory, rulingFamilySurname, Mac Giolla Phádraig]
-
A.
dynasticSurname
chosen
Indicates that the two entities share a family name associated with a particular dynasty or ruling lineage.
-
B.
lastRoyalHouseOf
Indicates that one entity is the final ruling royal house or dynasty associated with another entity, such as a realm, title, or political unit.
-
C.
dynasticSurnameAnglicisedAs
Indicates that a dynastic surname has an established or commonly used anglicized form derived from its original language.
-
D.
monarchInFamily
Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
-
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.