Triple
T31007052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donna Lindsay |
E790093
|
entity |
| Predicate | sharesFamilyLifeWith |
P151321
|
FINISHED |
| Object | Jonas Salk |
—
|
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: Jonas Salk | Statement: [Donna Lindsay, sharesFamilyLifeWith, Jonas Salk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesFamilyLifeWith Context triple: [Donna Lindsay, sharesFamilyLifeWith, Jonas Salk]
-
A.
sharesFamilyWith
chosen
Indicates that two entities belong to the same family or share a familial relationship.
-
B.
supportedFamilyLifeOf
Indicates that one entity provided assistance or resources that helped sustain or improve the family life or family-related well-being of another entity.
-
C.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
D.
cultFamily
Indicates that one entity is a family member of another within the context of a cult or cult-like group.
-
E.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: April 29, 2026, 8:57 p.m.