Triple
T29854133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 1 in C major (Moments musicaux, D. 780) |
E758139
|
entity |
| Predicate | hasScoreAvailable |
P180960
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [No. 1 in C major (Moments musicaux, D. 780), hasScoreAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoreAvailable Context triple: [No. 1 in C major (Moments musicaux, D. 780), hasScoreAvailable, true]
-
A.
hasScoreRecord
Indicates that an entity is associated with a specific score entry or scoring record.
-
B.
hasScoreCue
Indicates that one entity provides or is associated with a cue or signal used to determine, influence, or interpret the score of another entity.
-
C.
hasScoreCharacteristic
Indicates that one entity possesses or is associated with a particular scoring-related characteristic or property.
-
D.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
E.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 29, 2026, 5:45 p.m.