Triple
T25656554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sarod |
E643251
|
entity |
| Predicate | hasNumberOfSympatheticStrings |
P168895
|
FINISHED |
| Object | up to 15 |
—
|
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: up to 15 | Statement: [sarod, hasNumberOfSympatheticStrings, up to 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfSympatheticStrings Context triple: [sarod, hasNumberOfSympatheticStrings, up to 15]
-
A.
hasSympatheticStrings
Indicates that one object possesses strings designed to vibrate in sympathy with the vibrations of another sound source or set of strings.
-
B.
hasFundamentalStrings
Indicates that one entity possesses or is characterized by fundamental strings in relation to another entity or theoretical framework.
-
C.
hasFrets
Indicates that an instrument or similar object possesses frets, i.e., raised elements on its neck or surface that divide it into fixed pitch intervals.
-
D.
hasNumberOfDroneStrings
Indicates the relationship specifying how many drone strings are present in an instrument or musical setup.
-
E.
numberOfFrets
Indicates the specific count of frets associated with an instrument or fretboard.
- F. None of above. chosen
Provenance (4 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 21, 2026, 6:34 p.m.