Triple
T20116677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Song of India |
E490482
|
entity |
| Predicate | instrumentationInFamousRecording |
P12878
|
FINISHED |
| Object | trombone-led arrangement |
—
|
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: trombone-led arrangement | Statement: [Song of India, instrumentationInFamousRecording, trombone-led arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentationInFamousRecording Context triple: [Song of India, instrumentationInFamousRecording, trombone-led arrangement]
-
A.
notableInstrument
Indicates that an entity is especially known for playing or being associated with a particular musical instrument.
-
B.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
C.
discoveredWithInstrument
Indicates that something was discovered through the use of a specified instrument or tool.
-
D.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
E.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66739fde4819083e54f7435405bf0 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.