Triple
T6415513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greatest Hits Live |
E127816
|
entity |
| Predicate | hasMusicalRoleOfMainArtist |
P35860
|
FINISHED |
| Object | bassist |
—
|
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: bassist | Statement: [Greatest Hits Live, hasMusicalRoleOfMainArtist, bassist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalRoleOfMainArtist Context triple: [Greatest Hits Live, hasMusicalRoleOfMainArtist, bassist]
-
A.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
B.
hasMusicalArtistType
chosen
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
C.
hasMainPerformerOccupation
Indicates that an entity’s primary or main performer is associated with a specified occupation or professional role.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e89c2c81909eeedc234e8ccde2 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.