Triple
T37731175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Leconfield |
E940157
|
entity |
| Predicate | hasHeirType |
P196446
|
FINISHED |
| Object | heirs male of the body |
—
|
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: heirs male of the body | Statement: [Baron Leconfield, hasHeirType, heirs male of the body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeirType Context triple: [Baron Leconfield, hasHeirType, heirs male of the body]
-
A.
isHeirIn
Indicates that one entity is the designated heir within or under the inheritance rules of another entity (such as a person, estate, or legal framework).
-
B.
isHeirExpectedBy
Indicates that one entity is anticipated or designated to inherit from, succeed, or receive rights from another entity.
-
C.
hasHeirApparentFunction
Indicates that an entity has a designated heir apparent role or function assigned to it.
-
D.
hasHeirParticipant
Indicates that an entity participates in a relationship or event specifically in the role of an heir.
-
E.
hasHeirPresumptiveEligibility
Indicates that an entity is recognized as having a current, but potentially displaceable, right to inherit or succeed to a position, title, or estate.
- F. None of above. chosen
Provenance (4 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: May 3, 2026, 4:18 p.m.