Triple
T1114832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coming Home |
E11073
|
entity |
| Predicate | hasMusicalKey |
P12877
|
FINISHED |
| Object | popular music key (unspecified) |
—
|
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: popular music key (unspecified) | Statement: [Coming Home, hasMusicalKey, popular music key (unspecified)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalKey Context triple: [Coming Home, hasMusicalKey, popular music key (unspecified)]
-
A.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
B.
musicKey
chosen
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
C.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
-
D.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
E.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.