Triple
T26342097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monica Swinton |
E662673
|
entity |
| Predicate | motherFigureOf |
P139734
|
FINISHED |
| Object | David |
—
|
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: David | Statement: [Monica Swinton, motherFigureOf, David]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherFigureOf Context triple: [Monica Swinton, motherFigureOf, David]
-
A.
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.
-
B.
motherRole
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
C.
isMaternalFigureOf
chosen
Indicates a nurturing, protective, and guiding parental-like relationship that one individual has toward another, typically in a motherly role.
-
D.
motherMother
Indicates that one entity is the mother of another entity’s mother (i.e., the maternal grandmother relationship).
-
E.
motherType
Indicates the specific category or role of motherhood that one entity has in relation to another (e.g., biological, adoptive, step).
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:39 p.m.