Triple
T28298326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let the bright seraphim |
E713630
|
entity |
| Predicate | hasFamousTrumpetSoloists |
P83533
|
FINISHED |
| Object | Maurice André |
—
|
NE NERFINISHED |
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: Maurice André | Statement: [Let the bright seraphim, hasFamousTrumpetSoloists, Maurice André]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousTrumpetSoloists Context triple: [Let the bright seraphim, hasFamousTrumpetSoloists, Maurice André]
-
A.
hasSaxophoneSolos
Indicates that one or more saxophone solo performances occur within the referenced work, event, or context.
-
B.
hasPrincipalTrumpet
Indicates that one entity serves as the principal (lead) trumpet player for another entity, such as an orchestra or ensemble.
-
C.
trumpeter
chosen
Indicates that an entity plays the trumpet, typically as their role, profession, or primary musical activity in relation to another context or entity.
-
D.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
-
E.
notableComposersPerformed
Indicates that a subject has performed works composed by notable or distinguished composers.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 11:33 p.m.