Triple
T10039759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero |
E205263
|
entity |
| Predicate | mainInstrumentOfArtist |
P12601
|
FINISHED |
| Object | saxophone |
—
|
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: saxophone | Statement: [Hero, mainInstrumentOfArtist, saxophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInstrumentOfArtist Context triple: [Hero, mainInstrumentOfArtist, saxophone]
-
A.
featuresPrimaryInstrument
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
B.
primaryArtist
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
C.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
D.
hasNotableInstrumentNamedAfter
Indicates that an entity has a notable musical instrument that is named after it.
-
E.
playedInstrument
chosen
Indicates that an entity performed or used 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee186708190bc9fecd637b4f7e6 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.