Triple
T33346737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wes Craven’s New Nightmare |
E853814
|
entity |
| Predicate | portraysActorAsSelf |
P123658
|
FINISHED |
| Object | Heather Langenkamp |
—
|
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: Heather Langenkamp | Statement: [Wes Craven’s New Nightmare, portraysActorAsSelf, Heather Langenkamp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysActorAsSelf Context triple: [Wes Craven’s New Nightmare, portraysActorAsSelf, Heather Langenkamp]
-
A.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
B.
portraysPersonAs
Indicates that one entity represents, depicts, or characterizes another person in a particular way or role.
-
C.
hasCastMemberPlayingThemself
chosen
Indicates that a work includes a cast member who appears on screen portraying themself rather than a fictional character.
-
D.
leadActorPlaysVersionOfSelf
Indicates that the lead actor in a work portrays a character that is a version or representation of themselves.
-
E.
portraysRoleTrait
Indicates that one entity depicts or represents a particular role or character trait of 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69feba0f09508190b3e871c62b19ec7f |
completed | May 9, 2026, 4:37 a.m. |
| PD | Predicate disambiguation | batch_69feb957fe7c8190969fb31a6d1a59c8 |
completed | May 9, 2026, 4:34 a.m. |
Created at: May 1, 2026, 1:34 a.m.