Triple
T31274107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Matelots (ballet) |
E797469
|
entity |
| Predicate | hasComposerMembership |
P153739
|
FINISHED |
| Object | member of Les Six |
—
|
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: member of Les Six | Statement: [Les Matelots (ballet), hasComposerMembership, member of Les Six]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerMembership Context triple: [Les Matelots (ballet), hasComposerMembership, member of Les Six]
-
A.
hasBandMemberAsComposer
Indicates that a band has one of its own members serving as the composer of a musical work.
-
B.
hasNotablePerformerMembership
chosen
Indicates that an entity is or has been a distinguished or noteworthy member of a particular performer group, organization, or ensemble.
-
C.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
D.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
E.
hasBandMembership
Indicates that an entity is a member of, or belongs to, a particular band or musical group.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
Created at: April 29, 2026, 9:13 p.m.