Triple
T27041323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hewar |
E684496
|
entity |
| Predicate | primaryInstrumentOfMember |
P153597
|
FINISHED |
| Object | clarinet |
—
|
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: clarinet | Statement: [Hewar, primaryInstrumentOfMember, clarinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInstrumentOfMember Context triple: [Hewar, primaryInstrumentOfMember, clarinet]
-
A.
mainInstrumentOfMember
chosen
Indicates that a particular instrument is the primary instrument played by a specific member of a group or organization.
-
B.
notableInstrumentOfMember
Indicates that a particular musical instrument is especially associated with or prominently used by a given member of a group or organization.
-
C.
primaryInstrumentRole
Indicates that an entity serves as the main or leading instrument in a given role, context, or performance.
-
D.
primaryInstrumentAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
-
E.
primaryInstrumentFamily
Indicates the main family or category of musical instruments with which an entity is primarily associated.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 27, 2026, 8:05 a.m.