Triple
T29280141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man (music video) |
E742350
|
entity |
| Predicate | endCreditsFeature |
P47465
|
FINISHED |
| Object | behind-the-scenes footage |
—
|
LITERAL 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: behind-the-scenes footage | Statement: [The Man (music video), endCreditsFeature, behind-the-scenes footage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endCreditsFeature Context triple: [The Man (music video), endCreditsFeature, behind-the-scenes footage]
-
A.
hasPostCreditsScene
chosen
Indicates that a film or episode includes a scene that appears during or after the closing credits.
-
B.
featuresMidCreditsScene
Indicates that the work includes a special scene or content that appears during the middle of the closing credits.
-
C.
hasEndCreditsMusic
Indicates that an audiovisual work features specific music played during its end credits sequence.
-
D.
hasEndCreditsOrder
Indicates the sequence or position in which entities are listed in the end credits of a work.
-
E.
postCreditsSceneConnectsTo
Indicates that a post-credits scene is narratively or thematically linked to another work, scene, or installment in a franchise.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66514b8f8819083154cabcfc0efaa |
completed | May 2, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:54 p.m.