Triple
T16834284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shakuhachi |
E409230
|
entity |
| Predicate | notableRepertoireType |
P84416
|
FINISHED |
| Object | Zen Buddhist honkyoku solo pieces |
—
|
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: Zen Buddhist honkyoku solo pieces | Statement: [shakuhachi, notableRepertoireType, Zen Buddhist honkyoku solo pieces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRepertoireType Context triple: [shakuhachi, notableRepertoireType, Zen Buddhist honkyoku solo pieces]
-
A.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
-
B.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
C.
notableRecordingType
Indicates that the subject is notably associated with recordings of a particular type or format.
-
D.
featuresRepertoireType
chosen
Indicates that something includes or is associated with a particular type or category of repertoire.
-
E.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31981ac8190bbd9720efe842778 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.