Triple
T33853830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hitchcockian style |
E867710
|
entity |
| Predicate | exemplifiedInWork |
P93872
|
FINISHED |
| Object | Psycho |
—
|
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: Psycho | Statement: [Hitchcockian style, exemplifiedInWork, Psycho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exemplifiedInWork Context triple: [Hitchcockian style, exemplifiedInWork, Psycho]
-
A.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
-
B.
discussedInWorkOf
Indicates that a subject is examined, treated, or talked about within a particular work or publication.
-
C.
discoveredInWork
Indicates that something (such as an idea, object, or fact) was found, identified, or revealed within a particular work (such as a book, article, or artwork).
-
D.
appearsInWorkByTitle
chosen
Indicates that an entity appears in, is featured in, or is contained within a work identified by its title.
-
E.
portrayedInWork
Indicates that an entity is depicted or represented as a character, figure, or subject within a specific creative work.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70076bdec8190a109af85bed04c90 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.