Triple
T33560471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonwyck |
E859605
|
entity |
| Predicate | NicholasVanRynPortrayedBy |
P1507
|
FINISHED |
| Object | Vincent Price |
—
|
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: Vincent Price | Statement: [Dragonwyck, NicholasVanRynPortrayedBy, Vincent Price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NicholasVanRynPortrayedBy Context triple: [Dragonwyck, NicholasVanRynPortrayedBy, Vincent Price]
-
A.
James Pearson
Indicates a relationship or action involving the entity named "James Pearson" and another entity, event, or attribute, depending on context.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
portrayedBy
chosen
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
-
D.
Lincoln Lewis
Indicates a relationship or association involving the entity or name "Lincoln Lewis," such as authorship, participation, or attribution in a given context.
-
E.
Brian NiccolRole
Indicates that a specified role or position is held by, associated with, or pertains to Brian Niccol.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f7127d848190916a5a45fe3b6578 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.