Triple
T9905710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercy (remix) |
E185005
|
entity |
| Predicate | hasMusicalWorkType |
P91085
|
FINISHED |
| Object | song |
—
|
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: song | Statement: [Mercy (remix), hasMusicalWorkType, song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalWorkType Context triple: [Mercy (remix), hasMusicalWorkType, song]
-
A.
hasMusicalArtistType
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
B.
isMusicalWork
Indicates that one entity is a musical composition or piece created as an artistic work.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
musicalWork
Indicates a relationship where an entity is identified as a musical composition or piece associated with another entity (such as a creator, performance, or recording).
-
E.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
- F. None of above. chosen
Provenance (4 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb50cf8808190a41e565216712704 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:40 p.m.