Triple
T32660075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scherzo |
E834974
|
entity |
| Predicate | notableComposerUser |
P4321
|
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: [Scherzo, notableComposerUser, Ludwig van Beethoven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableComposerUser Context triple: [Scherzo, notableComposerUser, Ludwig van Beethoven]
-
A.
notableComposerOfType
Indicates that an entity is a well-known or distinguished composer associated with a specified type, category, or genre of composition.
-
B.
hasNotableComposer
chosen
Indicates that an entity is associated with a composer who is recognized as particularly significant or distinguished.
-
C.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
D.
favoriteComposer
Indicates that one entity is the preferred or most liked composer of another entity.
-
E.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3492b359a4819097d835b2909748ec |
completed | June 19, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:08 a.m.