Triple
T8776562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poison Arrow |
E208597
|
entity |
| Predicate | hasRemixOrExtendedVersion |
P83281
|
FINISHED |
| Object | extended mix |
—
|
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: extended mix | Statement: [Poison Arrow, hasRemixOrExtendedVersion, extended mix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemixOrExtendedVersion Context triple: [Poison Arrow, hasRemixOrExtendedVersion, extended mix]
-
A.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
B.
containsRemixes
Indicates that one entity includes or is associated with remix versions of another entity.
-
C.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
D.
hasRemixProducer
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical work).
-
E.
hasRemixType
chosen
Indicates that one creative work is a remix of another, specifying the particular type or style of remix relationship between them.
- 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_69ca835fbee88190bf625939bac48d7f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f5086088190b317cf2aac7bee83 |
completed | March 31, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:42 p.m.