Triple
T24279531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tanpura |
E605500
|
entity |
| Predicate | tunedRelativeTo |
P135075
|
FINISHED |
| Object | tonic (sa) |
—
|
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: tonic (sa) | Statement: [tanpura, tunedRelativeTo, tonic (sa)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunedRelativeTo Context triple: [tanpura, tunedRelativeTo, tonic (sa)]
-
A.
tunedBy
Indicates that one entity has been adjusted or calibrated in its settings, parameters, or configuration by another entity.
-
B.
tunedOrUntuned
Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
-
C.
usesTuningReference
chosen
Indicates that one entity adopts another entity as the pitch or frequency standard for tuning.
-
D.
tunable
Indicates that the associated entity can be adjusted or configured to different settings or values, typically to optimize performance or behavior.
-
E.
tuningType
Indicates the specific method or configuration by which something is adjusted or calibrated to achieve a desired 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f51050481908a9bd3c586702057 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.