Triple
T22493671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Medina de Rioseco |
E556082
|
entity |
| Predicate | titleInheritanceRule |
P83369
|
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: [House of Medina de Rioseco, titleInheritanceRule, primogeniture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInheritanceRule Context triple: [House of Medina de Rioseco, titleInheritanceRule, primogeniture]
-
A.
inheritsTitle
Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
-
B.
titleHolderRuled
Indicates that the entity holding a particular title exercised ruling authority or governance over another entity or domain.
-
C.
titleIsHereditary
chosen
Indicates that a title or rank is passed down through family lineage rather than being newly granted or earned each time.
-
D.
titleInheritanceYear
Indicates the year in which a title was inherited or passed on to a new holder.
-
E.
titleHierarchy
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb0dfb88190a4175e5e95d7ad4b |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.