Triple
T13463829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Rutland |
E311439
|
entity |
| Predicate | titleInheritsBy |
P23689
|
FINISHED |
| Object | male 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: male primogeniture | Statement: [Dukes of Rutland, titleInheritsBy, male primogeniture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInheritsBy Context triple: [Dukes of Rutland, titleInheritsBy, male primogeniture]
-
A.
inheritsTitle
chosen
Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
-
B.
titleDerivedFrom
Indicates that the title of one entity is obtained or adapted from another entity.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
titleBasis
Indicates that one entity serves as the basis or source material for the title or name of another entity.
-
E.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0f1830819085700b4521e44678 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:41 p.m.