Triple
T28727010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23rd Earl of Derby |
E730250
|
entity |
| Predicate | heirApparentGender |
P112001
|
FINISHED |
| Object | male |
—
|
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 | Statement: [23rd Earl of Derby, heirApparentGender, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heirApparentGender Context triple: [23rd Earl of Derby, heirApparentGender, male]
-
A.
genderOfChild
Indicates the gender or sex assigned to a specified child in the relationship.
-
B.
consideredHeirApparent
Indicates that one entity is regarded or treated as the likely or expected successor to another entity, typically in a position of authority or inheritance.
-
C.
heirApparentOf
Indicates that one entity is the officially recognized primary successor who is expected to inherit a title, position, or role from another entity.
-
D.
heirPresumptive
Indicates a person who is first in line to inherit a title, position, or estate but whose claim can be displaced by the birth of a more eligible heir.
-
E.
successorTitleGender
chosen
Indicates the gender associated with the person who succeeds another in a given title or position.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6570e85608190ab42f2a54e2bebb4 |
completed | May 2, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:56 a.m.