Triple
T9197421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cello Concerto |
E220750
|
entity |
| Predicate | hasOrchestralAccompaniment |
P5979
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cello Concerto, hasOrchestralAccompaniment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestralAccompaniment Context triple: [Cello Concerto, hasOrchestralAccompaniment, yes]
-
A.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
B.
hasPianoAccompaniment
Indicates that something (such as a musical work or performance) is accompanied by a piano part.
-
C.
performedWithOrchestra
chosen
Indicates that a performance or musical work was carried out in collaboration with an orchestra.
-
D.
hasMelodicOrchestration
Indicates that one entity provides or features the melodic orchestration for, or in association with, another entity.
-
E.
hasNoInstrumentalAccompaniment
Indicates that an action or event occurs without any instrumental musical accompaniment.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd87f50e88190940e73af1deda747 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.