Triple
T24279679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Yaman |
E605503
|
entity |
| Predicate | parentScaleRelation |
P46165
|
FINISHED |
| Object | derived from Kalyan thaat |
—
|
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: derived from Kalyan thaat | Statement: [Raga Yaman, parentScaleRelation, derived from Kalyan thaat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentScaleRelation Context triple: [Raga Yaman, parentScaleRelation, derived from Kalyan thaat]
-
A.
scaleRelation
Indicates a relationship where one quantity, object, or representation is proportionally larger or smaller than another according to a specific scale or factor.
-
B.
relatedScale
Indicates that two entities are connected through a common or comparable scale, measurement, or gradation system.
-
C.
associatedScale
chosen
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
-
D.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
E.
scalesBy
Indicates a relationship where one quantity, object, or representation is proportionally enlarged or reduced relative to another by a specific scaling factor.
- 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.