Triple
T37922319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Diabelli |
E945996
|
entity |
| Predicate | hasNotablePublishedComposer |
P80494
|
FINISHED |
| Object | Ludwig van Beethoven |
E7211
|
NE 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: Ludwig van Beethoven | Statement: [Anton Diabelli, hasNotablePublishedComposer, Ludwig van Beethoven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePublishedComposer Context triple: [Anton Diabelli, hasNotablePublishedComposer, Ludwig van Beethoven]
-
A.
hasNotableComposer
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
B.
publishedComposer
chosen
Indicates that a composer has had their musical works formally published, typically by a recognized publisher or label.
-
C.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
D.
hasMainComposerRole
Indicates that an entity holds the primary or leading composer role for a given work or production.
-
E.
hasNotableReleaseArtist
Indicates that an entity (such as a release or work) is associated with a notable artist responsible for its creation or performance.
- F. None of above.
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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117ef25b081908bf4f98c83dafcd8 |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.