Triple
T38665834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | II. Allegro appassionato |
E940450
|
entity |
| Predicate | hasAccompanyingEnsemble |
P55033
|
FINISHED |
| Object | symphony orchestra |
—
|
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: symphony orchestra | Statement: [II. Allegro appassionato, hasAccompanyingEnsemble, symphony orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccompanyingEnsemble Context triple: [II. Allegro appassionato, hasAccompanyingEnsemble, symphony orchestra]
-
A.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
B.
hasMusicalEnsemble
chosen
Indicates that one entity is associated with or includes a particular musical ensemble (such as a band, orchestra, or group) as part of its activities or composition.
-
C.
hasMusicalEnsembleType
Indicates that an entity is associated with or classified as a particular type of musical ensemble.
-
D.
hasEnsembles
Indicates that an entity is associated with one or more ensembles, typically as a member, component, or participant.
-
E.
sungByEnsemble
Indicates that a musical work or performance is vocally performed by a group of singers acting together as an ensemble.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:33 p.m.