Triple
T11753339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavatina: Adagio molto espressivo |
E279460
|
entity |
| Predicate | belongsToForm |
P28674
|
FINISHED |
| Object | multi-movement string quartet |
—
|
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: multi-movement string quartet | Statement: [Cavatina: Adagio molto espressivo, belongsToForm, multi-movement string quartet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToForm Context triple: [Cavatina: Adagio molto espressivo, belongsToForm, multi-movement string quartet]
-
A.
associatedWithForm
Indicates a relationship in which something is linked or connected to a particular form, document, or structured representation.
-
B.
belongTo
chosen
Indicates that one entity is a member, part, or property of another entity, signifying ownership, inclusion, or association.
-
C.
belongsToForceType
Indicates that an entity is associated with, or classified under, a specific type of force.
-
D.
belongsToLine
Indicates that an entity is a member or component of a particular line or linear grouping.
-
E.
belongsToInteraction
Indicates that one entity is part of, or associated as a component within, a specific interaction event or process.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.