Triple
T2577294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missa solemnis in D major, Op. 123 |
E57005
|
entity |
| Predicate | choralRequirement |
P4009
|
FINISHED |
| Object | large and skilled chorus |
—
|
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: large and skilled chorus | Statement: [Missa solemnis in D major, Op. 123, choralRequirement, large and skilled chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choralRequirement Context triple: [Missa solemnis in D major, Op. 123, choralRequirement, large and skilled chorus]
-
A.
hasChoir
chosen
Indicates that an entity possesses, maintains, or is associated with a choir.
-
B.
hasChorusBy
Indicates that something (typically a musical work or song) includes a chorus section that is performed, written, or provided by a specified entity.
-
C.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
-
D.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
E.
hasVocalPartInMovement
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.