Triple
T4207043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psycho |
E93807
|
entity |
| Predicate | editingFeature |
P20443
|
FINISHED |
| Object | rapid montage in shower scene |
—
|
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: rapid montage in shower scene | Statement: [Psycho, editingFeature, rapid montage in shower scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editingFeature Context triple: [Psycho, editingFeature, rapid montage in shower scene]
-
A.
coEditor
Indicates that two or more entities share responsibility for editing the same work or publication.
-
B.
editorStart
Indicates the point in time or position at which an editor begins working on, modifying, or reviewing a content item or resource.
-
C.
editingStyle
chosen
Indicates the characteristic manner or approach used when revising, arranging, or refining content.
-
D.
editorEnd
Indicates that an entity serves as the ending or concluding editor for a work, marking the final editorial responsibility in its production.
-
E.
notableEditor
Indicates that an entity has served as a significant or distinguished editor of another entity, such as a publication or 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:03 p.m.