Triple
T23163842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonate a tre, Op. 4 |
E578659
|
entity |
| Predicate | requiresContinuo |
P150142
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sonate a tre, Op. 4, requiresContinuo, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresContinuo Context triple: [Sonate a tre, Op. 4, requiresContinuo, yes]
-
A.
hasContinuo
chosen
Indicates that a musical work, section, or passage includes a basso continuo part or accompaniment.
-
B.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
C.
requiresApplicationOf
Indicates that performing one entity or process depends on actively applying or using another entity, method, or resource.
-
D.
continuedThrough
Indicates that an event, state, or process persisted without interruption across or beyond a specified point, period, or boundary.
-
E.
continuityCondition
Indicates that a relationship or process maintains consistency or unbroken progression across a boundary, interval, or sequence.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f29be30819091e18551044a98f3 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:02 p.m.