Triple
T8841754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hello (Adele song) |
E210403
|
entity |
| Predicate | musicVideoNotableFeature |
P3289
|
FINISHED |
| Object | shot in sepia tones |
—
|
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: shot in sepia tones | Statement: [Hello (Adele song), musicVideoNotableFeature, shot in sepia tones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoNotableFeature Context triple: [Hello (Adele song), musicVideoNotableFeature, shot in sepia tones]
-
A.
musicVideoNotableFor
Indicates that a music video is especially recognized or noteworthy for a particular feature, element, or aspect.
-
B.
musicVideoFeatures
chosen
Indicates that a music video includes or prominently showcases a particular person, group, or element.
-
C.
musicVideoNotableEvent
Indicates that a notable event is prominently featured in, associated with, or central to the context of a music video.
-
D.
musicVideoCameo
Indicates that one entity makes a brief or special-appearance role in the other entity’s music video.
-
E.
musicVideoFor
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60876c6c8190b1b490e447e1cf4b |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.