Triple
T27876939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hit ’Em High |
E704970
|
entity |
| Predicate | fromSoundtrack |
P46647
|
FINISHED |
| Object | Space Jam |
—
|
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: Space Jam | Statement: [Hit ’Em High, fromSoundtrack, Space Jam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fromSoundtrack Context triple: [Hit ’Em High, fromSoundtrack, Space Jam]
-
A.
sangSoundtrackFor
Indicates that one entity performed or recorded the soundtrack music for a work associated with another entity.
-
B.
isSoundtrackOf
Indicates that a piece of music or collection of music serves as the soundtrack for a particular work, such as a film, game, or show.
-
C.
isOnSoundtrack
chosen
Indicates that a piece of music is included as part of the official soundtrack for a particular work (such as a film, game, or show).
-
D.
hasSoundtrackCharacteristic
Indicates that a soundtrack possesses a specified quality, feature, or attribute.
-
E.
soundtrackType
Indicates the specific category or format of a soundtrack associated with a work, such as score, compilation, or original soundtrack.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6398047e081908137e619416f3e80 |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:27 p.m.