Triple
T38208901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Death Kiss |
E1009282
|
entity |
| Predicate | featuresActorPreviouslyIn |
P39600
|
FINISHED |
| Object | Dracula (1931 film) |
E261896
|
NE 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: Dracula (1931 film) | Statement: [The Death Kiss, featuresActorPreviouslyIn, Dracula (1931 film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresActorPreviouslyIn Context triple: [The Death Kiss, featuresActorPreviouslyIn, Dracula (1931 film)]
-
A.
previouslyPortrayedBy
Indicates that the subject entity was portrayed in the past by the specified actor or performer.
-
B.
laterFeaturedCastFrom
chosen
Indicates that one entity appears as a featured cast member in a later work, episode, or installment relative to another entity.
-
C.
featuresActorInMultipleRoles
Indicates that a work includes an actor who portrays more than one distinct role within that same work.
-
D.
actorKnownFor
Indicates that an actor is widely recognized or notable for a particular work, role, or contribution.
-
E.
followsInFilmography
Indicates that one work in a person’s filmography comes after another in chronological or credited order.
- F. None of above.
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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a418545089c81909ffcbc61a600aed0 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.