Triple
T36380845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 |
E896039
|
entity |
| Predicate | hasVirtuosicOrchestration |
P194286
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Symphony No. 3, hasVirtuosicOrchestration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVirtuosicOrchestration Context triple: [Symphony No. 3, hasVirtuosicOrchestration, true]
-
A.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
B.
isOrchestral
Indicates that something involves, is written for, or is performed by an orchestra.
-
C.
hasMelodicOrchestration
Indicates that one entity provides or features the melodic orchestration for, or in association with, another entity.
-
D.
performedWithOrchestra
Indicates that a performance or musical work was carried out in collaboration with an orchestra.
-
E.
hasOrchestralSuite
Indicates that a musical work is associated with, or has been arranged into, an orchestral suite derived from it.
- 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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: May 3, 2026, 4:10 p.m.