Triple
T9217459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Stark |
E221275
|
entity |
| Predicate | parentalIssue |
P86907
|
FINISHED |
| Object | strained relationship with his parents |
—
|
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: strained relationship with his parents | Statement: [Jim Stark, parentalIssue, strained relationship with his parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentalIssue Context triple: [Jim Stark, parentalIssue, strained relationship with his parents]
-
A.
parentalConflictWith
Indicates a relationship in which two parents are in disagreement, tension, or dispute with each other, often over child-related or family matters.
-
B.
parentalCare
Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
-
C.
parents
Indicates a parental relationship where one entity is the mother or father of another entity.
-
D.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
E.
parent
Indicates a relationship where one entity is the direct mother or father of another entity, from whom that other entity is descended.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda0ae3d081908ff3f5dab52df5ae |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc687067fc81909da2d78fda0cdcfb |
completed | April 1, 2026, 12:36 a.m. |
Created at: March 30, 2026, 7:27 p.m.