Triple
T13998582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | veena |
E336763
|
entity |
| Predicate | tunedFor |
P27295
|
FINISHED |
| Object | Carnatic raga performance |
—
|
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: Carnatic raga performance | Statement: [veena, tunedFor, Carnatic raga performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunedFor Context triple: [veena, tunedFor, Carnatic raga performance]
-
A.
tunedBy
Indicates that one entity has been adjusted or calibrated in its settings, parameters, or configuration by another entity.
-
B.
isTunedTo
chosen
Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
-
C.
tuning
Indicates the adjustment or calibration of something’s parameters or settings to achieve desired performance or behavior.
-
D.
tuningMethod
Indicates the method or approach used to adjust or optimize something’s parameters or performance.
-
E.
tunable
Indicates that the associated entity can be adjusted or configured to different settings or values, typically to optimize performance or behavior.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb81b208190a961e49a02fa4140 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.