Triple
T32172591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valentine Bluffs |
E821749
|
entity |
| Predicate | associatedWithRemakeReference |
P131205
|
FINISHED |
| Object | My Bloody Valentine 3D (2009) |
E46504
|
NE 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: My Bloody Valentine 3D (2009) | Statement: [Valentine Bluffs, associatedWithRemakeReference, My Bloody Valentine 3D (2009)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRemakeReference Context triple: [Valentine Bluffs, associatedWithRemakeReference, My Bloody Valentine 3D (2009)]
-
A.
hasRemakeRelationWith
chosen
Indicates that one work is a remake of, or has been remade as, another work, capturing the remake relationship between the two.
-
B.
remakeOfContext
Indicates that one context is a remake or re-creation of another pre-existing context, preserving core elements while producing a new version.
-
C.
associatedWithRelease
Indicates a relationship where something is linked or connected to a particular release event, version, or distribution.
-
D.
hasRemakeBy
Indicates that an original work has been remade or re-created by a specified agent (such as a person, studio, or organization).
-
E.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
- F. None of above.
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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bdaca388190ac7667ebccd1e649 |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:33 a.m.