Triple
T313180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto Barocco |
E7648
|
entity |
| Predicate | secondMovementTempo |
P1368
|
FINISHED |
| Object | Largo ma non tanto |
—
|
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: Largo ma non tanto | Statement: [Concerto Barocco, secondMovementTempo, Largo ma non tanto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMovementTempo Context triple: [Concerto Barocco, secondMovementTempo, Largo ma non tanto]
-
A.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
B.
tempo
chosen
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
C.
secondLetter
Indicates that one entity is the second letter (in sequence or position) of another entity, typically a string or word.
-
D.
secondSessionStart
Indicates the point in time when a second or subsequent session begins.
-
E.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.