Triple
T16255447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite española, Op. 47 |
E394614
|
entity |
| Predicate | frequentlyArrangedFor |
P122365
|
FINISHED |
| Object | 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: guitar | Statement: [Suite española, Op. 47, frequentlyArrangedFor, guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlyArrangedFor Context triple: [Suite española, Op. 47, frequentlyArrangedFor, guitar]
-
A.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
B.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
C.
canBeArrangedFor
Indicates that one entity is able to be scheduled, organized, or set up on behalf of or for the benefit of another entity.
-
D.
frequentlyPerformedAt
Indicates that an action or event occurs regularly or with high frequency at a particular location or context.
-
E.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.