Triple
T23872054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Taberna |
E592752
|
entity |
| Predicate | notableNumberOfMovementsWithinSection |
P32659
|
FINISHED |
| Object | multiple short movements |
—
|
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: multiple short movements | Statement: [In Taberna, notableNumberOfMovementsWithinSection, multiple short movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNumberOfMovementsWithinSection Context triple: [In Taberna, notableNumberOfMovementsWithinSection, multiple short movements]
-
A.
typicalMovementCountPerSymphony
Indicates the usual number of movements that a symphony typically contains.
-
B.
typicalMovementCountPerConcerto
Indicates the usual or standard number of movements that a concerto typically contains.
-
C.
typicalMovementCountPerQuintet
Indicates the usual number of movements contained within a five-part (quintet) grouping.
-
D.
movementCountFirstSonata
Indicates the number of movements contained in the first sonata.
-
E.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.