Triple
T6439598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messiah |
E138183
|
entity |
| Predicate | originalScoring |
P30391
|
FINISHED |
| Object | voices and orchestra |
—
|
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: voices and orchestra | Statement: [Messiah, originalScoring, voices and orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalScoring Context triple: [Messiah, originalScoring, voices and orchestra]
-
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.
featuresOriginalScore
chosen
Indicates that an entity includes or is accompanied by its initial, unaltered score or musical composition.
-
C.
scoringRecord
Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
-
D.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
E.
primaryScoringStyle
Indicates the main method or approach by which an entity achieves or generates scores or points.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06967241c8190965bac395adf2d03 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f96980819091bab9335922a457 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:45 p.m.