Triple
T33730971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky film series scores |
E864272
|
entity |
| Predicate | composerOfRocky |
P155528
|
FINISHED |
| Object | Bill Conti |
—
|
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: Bill Conti | Statement: [Rocky film series scores, composerOfRocky, Bill Conti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOfRocky Context triple: [Rocky film series scores, composerOfRocky, Bill Conti]
-
A.
composerOfMainWork
chosen
Indicates that one entity is the composer who created the primary or main work associated with another entity.
-
B.
soundtrackComposerCollaboratedWith
Indicates that a soundtrack composer worked together with another person or entity in creating or producing a soundtrack.
-
C.
directorAlsoComposedMusic
Indicates that the person who directed the work also composed its musical score.
-
D.
composerOfCataloguedWork
Indicates that one entity is the composer or creator of a specific catalogued musical or artistic work associated with another entity.
-
E.
composerOfOriginalVersion
Indicates that one entity is the creator or composer of the original version of a work, before any adaptations, arrangements, or derivative versions.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:44 a.m.