Triple
T29659711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French school of flute playing |
E750371
|
entity |
| Predicate | usesPrimaryInstrumentType |
P54631
|
FINISHED |
| Object | Boehm-system flute |
—
|
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: Boehm-system flute | Statement: [French school of flute playing, usesPrimaryInstrumentType, Boehm-system flute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPrimaryInstrumentType Context triple: [French school of flute playing, usesPrimaryInstrumentType, Boehm-system flute]
-
A.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
B.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
C.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
D.
featuresPrimaryInstrument
chosen
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 6:57 p.m.