Triple
T37456151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leah |
E930804
|
entity |
| Predicate | grandfatherFigure |
P61441
|
FINISHED |
| Object | Deckard Cain |
—
|
NE NERFINISHED |
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: Deckard Cain | Statement: [Leah, grandfatherFigure, Deckard Cain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandfatherFigure Context triple: [Leah, grandfatherFigure, Deckard Cain]
-
A.
grandmotherFigure
Indicates a relationship where one entity serves in a grandmother-like, nurturing or elder female caregiver role toward another, regardless of biological or legal kinship.
-
B.
grandfather
Indicates that one entity is the male parent of another entity’s parent.
-
C.
grandfatherIs
chosen
Indicates that one entity is the grandfather (parent of a parent) of another entity.
-
D.
fatherFigure
Indicates a relationship where one entity serves in a paternal or mentoring role toward another, providing guidance, support, or care similar to that of a father.
-
E.
grandfatherRole
Indicates that one entity holds the familial role of grandfather in relation 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:17 p.m.