Triple
T25282470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mridangam |
E633856
|
entity |
| Predicate | primaryPercussionInstrumentOf |
P158362
|
FINISHED |
| Object | Carnatic music |
—
|
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: Carnatic music | Statement: [Mridangam, primaryPercussionInstrumentOf, Carnatic music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPercussionInstrumentOf Context triple: [Mridangam, primaryPercussionInstrumentOf, Carnatic music]
-
A.
percussionType
chosen
Indicates the specific kind or category of percussion instrument associated with an entity.
-
B.
primaryInstrumentFamily
Indicates the main family or category of musical instruments with which an entity is primarily associated.
-
C.
percussion
Indicates that an entity produces sound by being struck, shaken, or otherwise hit, as in playing or functioning as a percussion instrument.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
primaryInstrumentAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 21, 2026, 1:19 p.m.