Triple
T24279656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Yaman |
E605503
|
entity |
| Predicate | omitsSwar |
P3119
|
FINISHED |
| Object | Shuddha Ma |
—
|
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: Shuddha Ma | Statement: [Raga Yaman, omitsSwar, Shuddha Ma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: omitsSwar Context triple: [Raga Yaman, omitsSwar, Shuddha Ma]
-
A.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
B.
excludesSense
Indicates that one sense or interpretation explicitly rules out or is incompatible with another sense.
-
C.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
D.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
E.
avoidsPronunciationOf
Indicates that one entity deliberately refrains from saying or articulating the name, word, or expression associated with another entity.
- 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.