Triple
T9801901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Bloody Valentine |
E237857
|
entity |
| Predicate | editedVersion |
P90050
|
FINISHED |
| Object | censored theatrical cut |
—
|
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: censored theatrical cut | Statement: [My Bloody Valentine, editedVersion, censored theatrical cut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editedVersion Context triple: [My Bloody Valentine, editedVersion, censored theatrical cut]
-
A.
editedVersionLength
Indicates the length or duration of something after it has been edited or modified from its original form.
-
B.
updatedEdition
Indicates that one entity is a newer or revised edition of another entity.
-
C.
revisedVersionLanguage
Indicates that one entity is a revised version of another, specifically with respect to its language or linguistic form.
-
D.
reworkedVersionStyle
Indicates that one entity is a version of another that has been modified or reinterpreted in a different style.
-
E.
editedIn
Indicates that an entity was modified, revised, or otherwise altered within a particular context, tool, environment, or time frame.
- F. None of above. chosen
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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62b41048190bcef70a7591830c6 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:29 p.m.