Triple
T18188683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlophone PMC 1240 (mono) |
E435477
|
entity |
| Predicate | isOriginalMix |
P130156
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Parlophone PMC 1240 (mono), isOriginalMix, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOriginalMix Context triple: [Parlophone PMC 1240 (mono), isOriginalMix, true]
-
A.
hasOriginalMusicBy
Indicates that the original musical score or soundtrack for a work was created or composed by a specified entity.
-
B.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
C.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
D.
containsOriginalSongs
Indicates that one entity includes or features songs that are original compositions rather than covers or adaptations.
-
E.
originallyInstrumental
Indicates that an entity was initially used as the instrument or means by which an action or effect was brought about, especially when this instrumental role may have changed over time.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e00059d4819097f681e702fe49e6 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:31 a.m.