Triple
T23838542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Notation I for solo piano |
E590919
|
entity |
| Predicate | hasTypeOfScoring |
P141114
|
FINISHED |
| Object | solo |
—
|
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: solo | Statement: [Notation I for solo piano, hasTypeOfScoring, solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfScoring Context triple: [Notation I for solo piano, hasTypeOfScoring, solo]
-
A.
hasScoreType
chosen
Indicates that an entity is associated with a particular type or category of score.
-
B.
scoringType
Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
-
C.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
-
D.
hasScorer
Indicates that one entity serves as the scorer (e.g., the one who scores points, goals, or evaluations) in relation to another entity.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c884c800819090d301740e1966cc |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.