Triple
T16255519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asturias (Leyenda) |
E394616
|
entity |
| Predicate | popularizedOnInstrument |
P9123
|
FINISHED |
| Object | classical guitar |
—
|
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: classical guitar | Statement: [Asturias (Leyenda), popularizedOnInstrument, classical guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularizedOnInstrument Context triple: [Asturias (Leyenda), popularizedOnInstrument, classical guitar]
-
A.
introducedInstrument
Indicates that one entity caused or brought about the initial use or adoption of a particular instrument by another entity or within a given context.
-
B.
notableInstrument
chosen
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
C.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
D.
influencedInstrument
Indicates that one entity has affected, shaped, or altered a musical instrument or tool in some way, such as its design, use, style, or development.
-
E.
inspiredInstrument
Indicates that one entity served as the creative inspiration or model for the design, creation, or development of another 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459a48f081909c76b38741b8f04e |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.