Triple
T24956608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Seaham |
E624489
|
entity |
| Predicate | inheritedByPrimogeniture |
P48009
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Viscount Seaham, inheritedByPrimogeniture, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritedByPrimogeniture Context triple: [Viscount Seaham, inheritedByPrimogeniture, yes]
-
A.
madeHeirBy
Indicates that one entity is designated or appointed as the heir of another entity.
-
B.
clanInheritance
Indicates that rights, titles, or property are passed down within a clan according to its internal rules of succession.
-
C.
dynasticInheritance
chosen
Indicates that rights, titles, or property are passed down through a family line according to established rules of succession.
-
D.
heirThroughFemaleLine
Indicates that one entity is the heir of another specifically through a lineage traced via female ancestors.
-
E.
isNextInLineOfSuccessionTo
Indicates that one entity is the immediate heir or successor designated to take over a position, title, or role when the current holder can no longer occupy it.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f424044cf8819092105c93ceba3b9c |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:57 a.m.