Triple
T21489885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passion Flower |
E530208
|
entity |
| Predicate | instrumentalFocus |
P12878
|
FINISHED |
| Object | alto saxophone |
—
|
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: alto saxophone | Statement: [Passion Flower, instrumentalFocus, alto saxophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentalFocus Context triple: [Passion Flower, instrumentalFocus, alto saxophone]
-
A.
primaryInstrumentalFocus
Indicates that one entity serves as the main or most emphasized instrument or means by which another entity performs an action or achieves an effect.
-
B.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
-
C.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
D.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
-
E.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea39e73081908e8d14118f9d1e03 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.