Triple
T31430310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Max: Fury Road (film score) |
E801777
|
entity |
| Predicate | composerAlias |
P132024
|
FINISHED |
| Object | Junkie XL |
—
|
NE NERFINISHED |
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: [Mad Max: Fury Road (film score), composerAlias, Junkie XL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerAlias Context triple: [Mad Max: Fury Road (film score), composerAlias, Junkie XL]
-
A.
composer
Indicates that one entity is the creator or writer of a musical work associated with another entity.
-
B.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
C.
composerPackageName
chosen
Indicates the name assigned to a software package in the Composer dependency management system.
-
D.
gaveAliasTo
Indicates that one entity assigned or provided an alternative name or alias to another entity.
-
E.
usesAliasConvention
Indicates that one entity adopts or follows a specific alias-naming convention when referring to another entity.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 30, 2026, 8:57 p.m.