Triple
T31143145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzpatrick of Upper Ossory |
E793843
|
entity |
| Predicate | laterSuccession |
P171639
|
FINISHED |
| Object | primogeniture |
—
|
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: primogeniture | Statement: [Fitzpatrick of Upper Ossory, laterSuccession, primogeniture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSuccession Context triple: [Fitzpatrick of Upper Ossory, laterSuccession, primogeniture]
-
A.
laterHeir
Indicates that one entity becomes the heir of another at a later time, succeeding a prior heir or following a change in succession.
-
B.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
C.
hasLineOfSuccession
Indicates that one entity is designated to follow or replace another in a defined order of succession.
-
D.
usedSuccessionSystem
chosen
Indicates that an entity employed a particular system or method for determining succession or inheritance of position, title, or authority.
-
E.
governsSuccessionOf
Indicates that an entity establishes or controls the rules or process by which another entity’s position, title, or role is passed on to successors.
- 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_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: April 29, 2026, 9:06 p.m.