Triple
T15417935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daddy (feat. October London) |
E369295
|
entity |
| Predicate | musicalRoleOfOctoberLondon |
P24740
|
FINISHED |
| Object | featured vocalist |
—
|
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: featured vocalist | Statement: [Daddy (feat. October London), musicalRoleOfOctoberLondon, featured vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalRoleOfOctoberLondon Context triple: [Daddy (feat. October London), musicalRoleOfOctoberLondon, featured vocalist]
-
A.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
B.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
C.
musicalCharacter
Indicates that one entity is a character or role that appears within the other entity, which is a musical work or production.
-
D.
musicSceneRole
Indicates the specific function or position an entity holds within a particular music scene or musical community.
-
E.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ebce4f48190ba282ecb4fb2f6fa |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.