Triple
T16514855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hymnes |
E401154
|
entity |
| Predicate | isScoreType |
P115017
|
FINISHED |
| Object | full orchestral score |
—
|
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: full orchestral score | Statement: [Hymnes, isScoreType, full orchestral score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScoreType Context triple: [Hymnes, isScoreType, full orchestral score]
-
A.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
B.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
C.
isScoreForGenre
Indicates that a given score or rating is specifically associated with a particular genre.
-
D.
isPartOfScoreBy
Indicates that something constitutes a component or segment within a larger score or musical composition.
-
E.
hasScoreCharacteristic
chosen
Indicates that one entity possesses or is associated with a particular scoring-related characteristic or property.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7a5ff88190984e2f2bc2fd17cc |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.