Triple
T4897569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Band of Gold |
E109718
|
entity |
| Predicate | notabilityInRepertoire |
P60535
|
FINISHED |
| Object | enduring appeal |
—
|
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: enduring appeal | Statement: [Band of Gold, notabilityInRepertoire, enduring appeal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notabilityInRepertoire Context triple: [Band of Gold, notabilityInRepertoire, enduring appeal]
-
A.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
organNotability
Indicates that an organ is notable or significant in some specific context or for a particular purpose.
-
C.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
D.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
E.
musicalAbility
Indicates that an entity possesses skill, talent, or proficiency in performing, creating, or understanding music.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd7060f9988190afdf98eb0a38515d |
completed | March 20, 2026, 4:05 p.m. |
Created at: March 20, 2026, 1:28 p.m.