Triple
T33075484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Scherzo: Allegro pesante |
E846349
|
entity |
| Predicate | orderInSymphony |
P15216
|
FINISHED |
| Object | third 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: third movement | Statement: [III. Scherzo: Allegro pesante, orderInSymphony, third movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInSymphony Context triple: [III. Scherzo: Allegro pesante, orderInSymphony, third movement]
-
A.
orderInComposerSymphonies
Indicates the sequential position that a particular symphony occupies within the complete set of symphonies composed by a given composer.
-
B.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
compositionOrder
Indicates the sequence in which components or elements are combined or arranged to form a whole.
-
D.
componentOrder
chosen
Indicates the relative sequence or arrangement of components within a larger structure or system.
-
E.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:25 a.m.