Triple
T32163798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BURN-E |
E821501
|
entity |
| Predicate | hasEndCreditsSong |
P118047
|
FINISHED |
| Object | “Down to Earth” (instrumental excerpt) |
—
|
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: “Down to Earth” (instrumental excerpt) | Statement: [BURN-E, hasEndCreditsSong, “Down to Earth” (instrumental excerpt)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndCreditsSong Context triple: [BURN-E, hasEndCreditsSong, “Down to Earth” (instrumental excerpt)]
-
A.
hasEndCreditsMusic
chosen
Indicates that an audiovisual work features specific music played during its end credits sequence.
-
B.
hasEndCreditsOrder
Indicates the sequence or position in which entities are listed in the end credits of a work.
-
C.
hasPostCreditsScene
Indicates that a film or episode includes a scene that appears during or after the closing credits.
-
D.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
E.
hasThemeSong
Indicates that an entity is associated with or characterized by a particular theme song.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 12:33 a.m.