Triple
T9036455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernstein catalog: BB 51 |
E216505
|
entity |
| Predicate | workScoring |
P85810
|
FINISHED |
| Object | mixed 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: mixed chorus | Statement: [Bernstein catalog: BB 51, workScoring, mixed chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workScoring Context triple: [Bernstein catalog: BB 51, workScoring, mixed chorus]
-
A.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
B.
individualScoring
Indicates that a specific individual receives or is assigned a particular score or evaluation in a given context.
-
C.
scoreAssignment
Indicates evaluating and assigning a grade or numerical score to an assignment.
-
D.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
- F. None of above. chosen
Provenance (4 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_69ca83d10b608190b2b2f8e0a7faaf14 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6ac0b00c8190a7250b86bb7cc276 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.