Triple
T5347344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven symphony cycles |
E124087
|
entity |
| Predicate | hasRepertoireType |
P3738
|
FINISHED |
| Object | complete symphony set |
—
|
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: complete symphony set | Statement: [Beethoven symphony cycles, hasRepertoireType, complete symphony set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepertoireType Context triple: [Beethoven symphony cycles, hasRepertoireType, complete symphony set]
-
A.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
C.
hasCorpusType
Indicates the type or category of corpus associated with an entity (e.g., text, speech, multimodal).
-
D.
hasMusicalEnsembleType
Indicates that an entity is associated with or classified as a particular type of musical ensemble.
-
E.
hasRiffType
Indicates that one entity is characterized by, or associated with, a specific type or category of riff.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85ede7c481908347d557aa4d19ad |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.