Triple
T24252028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patricia Poole |
E603555
|
entity |
| Predicate | familyLifeWith |
P47635
|
FINISHED |
| Object | Dick Van Patten |
—
|
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: Dick Van Patten | Statement: [Patricia Poole, familyLifeWith, Dick Van Patten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyLifeWith Context triple: [Patricia Poole, familyLifeWith, Dick Van Patten]
-
A.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
-
B.
familyContext
chosen
Indicates that the entities are related or associated within a family or household context, such as kinship, caregiving, or shared domestic life.
-
C.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
-
D.
familyApplication
Indicates that an application or request is made in the context of a family relationship, typically involving or affecting multiple family members.
-
E.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8aff788190bb37fc8ab04bde00 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.