Triple
T35333561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kindred the Family Soul |
E1020390
|
entity |
| Predicate | spouseOfWithinGroup |
P92968
|
FINISHED |
| Object | Fatin Dantzler and Aja Graydon |
—
|
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: Fatin Dantzler and Aja Graydon | Statement: [Kindred the Family Soul, spouseOfWithinGroup, Fatin Dantzler and Aja Graydon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfWithinGroup Context triple: [Kindred the Family Soul, spouseOfWithinGroup, Fatin Dantzler and Aja Graydon]
-
A.
spouseMemberOf
Indicates that a person’s spouse is a member of a specified group, organization, or entity.
-
B.
spouseOfType
Indicates that one entity is the spouse of another, specifying the type or role of that spousal relationship.
-
C.
spouseOfSequence
Indicates a sequential or ordered relationship of being spouses, where each entity is married to the next in the sequence.
-
D.
spouseInFamily
chosen
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
E.
spouseInstanceOf
Indicates that one entity is the specific spouse (marriage partner) instance of 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 3, 2026, 4:03 p.m.