Triple
T31353913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canzonetta: Andante |
E799674
|
entity |
| Predicate | positionInConcerto |
P86740
|
FINISHED |
| Object | second movement |
—
|
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: second movement | Statement: [Canzonetta: Andante, positionInConcerto, second movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInConcerto Context triple: [Canzonetta: Andante, positionInConcerto, second movement]
-
A.
positionInTrio
Indicates the specific ordered place an entity occupies within a three-member group or trio.
-
B.
positionOnInstruments
Indicates the specific role or seat an individual holds within a group of instruments, such as in an orchestra or ensemble.
-
C.
positionInAct
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
-
D.
positionInPerformance
chosen
Indicates the specific ordering or placement of an entity within a performance or sequence of performed elements.
-
E.
positionInOpus
Indicates the specific location or ordering of a part or element within a larger work or opus.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 29, 2026, 9:17 p.m.