Triple
T17317974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor de Bohun |
E420478
|
entity |
| Predicate | coHeir |
P95059
|
FINISHED |
| Object | de Bohun estates |
—
|
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: de Bohun estates | Statement: [Eleanor de Bohun, coHeir, de Bohun estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coHeir Context triple: [Eleanor de Bohun, coHeir, de Bohun estates]
-
A.
coHeirWith
chosen
Indicates that two or more entities jointly inherit or share rights to the same estate, title, or legacy.
-
B.
coHeads
Indicates that two or more entities jointly hold the primary leadership or head position of the same organization, group, or initiative.
-
C.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
-
D.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
-
E.
futureHeir
Indicates that one entity is designated or expected to inherit from another entity at a future time.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399ea7dc8190a0ecab7534fe16c3 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.