Triple
T31878325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowager Duchess |
E813804
|
entity |
| Predicate | mayBeStepRelativeOf |
P28649
|
FINISHED |
| Object | current duke |
—
|
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: current duke | Statement: [Dowager Duchess, mayBeStepRelativeOf, current duke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeStepRelativeOf Context triple: [Dowager Duchess, mayBeStepRelativeOf, current duke]
-
A.
mayBeRelativeIn
Indicates that one entity is possibly, but not certainly, a relative (family-related) of another entity.
-
B.
hasStepSibling
Indicates that one person is the step-sibling of another, meaning they are related through the marriage of their parents rather than by blood or adoption.
-
C.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
D.
stepRelative
chosen
Indicates a familial relationship where one person is a step-relative of another, such as a step-parent, step-child, or step-sibling, created through marriage rather than blood or adoption.
-
E.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 30, 2026, 11:55 p.m.