Triple
T29049796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vincent Price as Nicholas Medina |
E735234
|
entity |
| Predicate | dominantTrait |
P69510
|
FINISHED |
| Object | tormented |
—
|
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: tormented | Statement: [Vincent Price as Nicholas Medina, dominantTrait, tormented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantTrait Context triple: [Vincent Price as Nicholas Medina, dominantTrait, tormented]
-
A.
dominantGeneration
Indicates that one generation in a life cycle is more prominent, long-lived, or visually conspicuous than the other generation(s).
-
B.
dominatingFeature
chosen
Indicates that one feature stands out as the most prominent or influential characteristic in relation to others.
-
C.
dominantClass
Indicates that one class or category holds primary authority, influence, or precedence over others within a given context.
-
D.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
E.
dominantComplex
Indicates that one entity exerts primary control, influence, or prominence over another within a given context or system.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 28, 2026, 10:07 a.m.