Triple
T24697953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Johnson Stover |
E611648
|
entity |
| Predicate | hasMotherRole |
P102151
|
FINISHED |
| Object | First Lady of the United States |
—
|
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: First Lady of the United States | Statement: [Mary Johnson Stover, hasMotherRole, First Lady of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotherRole Context triple: [Mary Johnson Stover, hasMotherRole, First Lady of the United States]
-
A.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
B.
motherRole
chosen
Indicates that one entity holds the role or function of a mother in relation to another entity.
-
C.
isMaternalFigureOf
Indicates a nurturing, protective, and guiding parental-like relationship that one individual has toward another, typically in a motherly role.
-
D.
motherIs
Indicates that one entity is the mother (biological or adoptive) of another entity.
-
E.
notMotherOf
Indicates that the subject is explicitly not the mother (biological, adoptive, or recognized maternal parent) of the object.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 3:22 a.m.