Triple
T37353506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puddle Monkey Productions |
E927389
|
entity |
| Predicate | roleInSisterWives |
P203782
|
FINISHED |
| Object | production company |
—
|
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: production company | Statement: [Puddle Monkey Productions, roleInSisterWives, production company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSisterWives Context triple: [Puddle Monkey Productions, roleInSisterWives, production company]
-
A.
Sister Wives_focus
Indicates a focus relationship where attention, narrative, or discussion is centered on the subject in the context of the "Sister Wives" relationship or scenario.
-
B.
collectiveRoleWithSisters
Indicates a shared or joint role that an entity holds together with its sisters as a collective group.
-
C.
spouseIsSisterOf
Indicates that a person’s spouse is also the sister of another specified individual.
-
D.
spouseMission
Indicates that one person is the spouse of another specifically in the context of a particular mission or assignment.
-
E.
roleInMarriage
Indicates the specific role or position an individual holds within a marriage relationship (e.g., spouse, husband, wife).
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02008fcf1c8190b5b6c285944c52e9 |
completed | May 11, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_6a01ffd3ba008190b6f026bd4e6b9a37 |
completed | May 11, 2026, 4:12 p.m. |
| PDg | Predicate description generation | batch_6a02008eb6ac81908f66e8e07e0726c6 |
completed | May 11, 2026, 4:15 p.m. |
Created at: May 3, 2026, 4:16 p.m.