Triple
T34381665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patsy Beck |
E882453
|
entity |
| Predicate | spouseFatherInLawNotableFor |
P195868
|
FINISHED |
| Object | classic horror roles |
—
|
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: classic horror roles | Statement: [Patsy Beck, spouseFatherInLawNotableFor, classic horror roles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseFatherInLawNotableFor Context triple: [Patsy Beck, spouseFatherInLawNotableFor, classic horror roles]
-
A.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouseNotableAncestor
Indicates that a person’s spouse has an ancestor who is notable or historically significant.
-
C.
spouse notableWork
Indicates that a person's spouse is significantly associated with a particular notable work.
-
D.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
fatherNotableAs
Indicates that someone is recognized or distinguished specifically in their role as a father.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:59 a.m.