Triple
T13607966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover Beach, Op. 3 |
E325113
|
entity |
| Predicate | usesEnsembleType |
P25465
|
FINISHED |
| Object | 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: string quartet | Statement: [Dover Beach, Op. 3, usesEnsembleType, string quartet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEnsembleType Context triple: [Dover Beach, Op. 3, usesEnsembleType, string quartet]
-
A.
requiresEnsemble
Indicates that performing or realizing one entity necessitates the coordinated participation of multiple entities acting together as an ensemble.
-
B.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
-
C.
typicalEnsembleType
chosen
Indicates the usual or characteristic type of ensemble associated with or used to perform a given work, piece, or musical context.
-
D.
hasEnsembles
Indicates that an entity is associated with one or more ensembles, typically as a member, component, or participant.
-
E.
associatedEnsembleOf
Indicates that one entity is linked or connected to a particular ensemble, typically as a member, contributor, or related component of that group.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.