Triple
T23189096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deveraux Octavian Basil Jagger |
E579680
|
entity |
| Predicate | positionInPaternalChildren |
P20593
|
FINISHED |
| Object | youngest son |
—
|
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: youngest son | Statement: [Deveraux Octavian Basil Jagger, positionInPaternalChildren, youngest son]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPaternalChildren Context triple: [Deveraux Octavian Basil Jagger, positionInPaternalChildren, youngest son]
-
A.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
-
B.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
C.
parentPosition
Indicates that one entity occupies the role of a parent or higher-level position relative to another entity in a hierarchical structure.
-
D.
positionHeldByParent
Indicates that a position or role is held by the parent of the referenced entity.
-
E.
positionInPatriarchs
Indicates the specific rank or placement an individual holds within a defined lineage or hierarchy of patriarchs.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd592248190a7e705c554885cd1 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.