Triple
T35281094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-flat clarinet |
E1018933
|
entity |
| Predicate | hasNotableSoloWorksBy |
P33590
|
FINISHED |
| Object | Jean Françaix |
E1880791
|
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: Jean Françaix | Statement: [E-flat clarinet, hasNotableSoloWorksBy, Jean Françaix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSoloWorksBy Context triple: [E-flat clarinet, hasNotableSoloWorksBy, Jean Françaix]
-
A.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
B.
hasNotableMusicWork
chosen
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
-
C.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
-
D.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
E.
hasNotableWorkCollection
Indicates that an entity is associated with a collection of its notable works or creations.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a380fc313f88190a6333d1b2aa19b0f |
completed | June 21, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.