Triple
T35314972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The 12th Man – score |
E1019876
|
entity |
| Predicate | creditedComposerName |
P47024
|
FINISHED |
| Object | Christophe Beck |
—
|
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: Christophe Beck | Statement: [The 12th Man – score, creditedComposerName, Christophe Beck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedComposerName Context triple: [The 12th Man – score, creditedComposerName, Christophe Beck]
-
A.
creditedMusician
Indicates that a musician is formally acknowledged as having contributed to a particular musical work or recording.
-
B.
recordedComposer
Indicates that one entity has made an audio or video recording of a musical work composed by another entity.
-
C.
creditedSongwritersOfSampledWork
Indicates that the related entities are the songwriters who received official credit for the original work that was sampled in another piece of music.
-
D.
artistNameCredit
Indicates that a specific artist is credited by name for their contribution to a work or production.
-
E.
hasMusicalComposer
chosen
Indicates that one entity serves as the musical composer responsible for creating the music associated with 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.