Triple
T33075504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Scherzo: Allegro pesante |
E846349
|
entity |
| Predicate | positionInForm |
P198469
|
FINISHED |
| Object | follows Largo |
—
|
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: follows Largo | Statement: [III. Scherzo: Allegro pesante, positionInForm, follows Largo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInForm Context triple: [III. Scherzo: Allegro pesante, positionInForm, follows Largo]
-
A.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
B.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
C.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
D.
positionInPage
Indicates the specific location or placement of an element within a page’s layout or structure.
-
E.
positionInFrame
Indicates the spatial location or coordinates of an entity within a specific frame or reference image.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
| PDg | Predicate description generation | batch_69fee690af688190a845310f102a0c83 |
completed | May 9, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:25 a.m.