Triple
T33057918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Lloyd family |
E845892
|
entity |
| Predicate | hasSpouseInLineage |
P194768
|
FINISHED |
| Object | Mildred Davis |
—
|
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: Mildred Davis | Statement: [Harold Lloyd family, hasSpouseInLineage, Mildred Davis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpouseInLineage Context triple: [Harold Lloyd family, hasSpouseInLineage, Mildred Davis]
-
A.
hasSpousePositionInFamily
Indicates that a person’s spouse holds a specific role or position within the family structure.
-
B.
spouseOfPersonWithParent
Indicates that one person is the spouse of another person who is a parent (i.e., married to someone who has at least one child).
-
C.
spouseNotableAncestor
Indicates that a person’s spouse has an ancestor who is notable or historically significant.
-
D.
spouseOfDescendantOf
Indicates that one entity is the spouse of a person who is a descendant of another entity.
-
E.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
- F. None of above. chosen
Provenance (4 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: May 1, 2026, 1:25 a.m.