Triple
T31430426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice League (2017 film score contributions) |
E801780
|
entity |
| Predicate | primaryComposerReplaced |
P117742
|
FINISHED |
| Object | Junkie XL |
E195754
|
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: Junkie XL | Statement: [Justice League (2017 film score contributions), primaryComposerReplaced, Junkie XL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryComposerReplaced Context triple: [Justice League (2017 film score contributions), primaryComposerReplaced, Junkie XL]
-
A.
primaryReplacementFor
chosen
Indicates that one entity serves as the main or preferred substitute or successor for another entity.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
coverComposer
Indicates that one entity is the composer of the music for another entity that is a cover version of a work.
-
D.
compositionChanged
Indicates that the makeup or constituent elements of something have been altered from a previous state.
-
E.
alternateScoreComposer
Indicates that an entity serves as an alternative or secondary composer associated with a given score.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b849b3ed48190a19f2526ac318de7 |
completed | June 12, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 8:57 p.m.