Triple
T24747895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Kafi |
E619053
|
entity |
| Predicate | hasArohana |
P157289
|
FINISHED |
| Object | S R g m P D n S' |
—
|
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: S R g m P D n S' | Statement: [Raga Kafi, hasArohana, S R g m P D n S']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArohana Context triple: [Raga Kafi, hasArohana, S R g m P D n S']
-
A.
aroha
Indicates a relationship of love, affection, or deep caring directed from one entity toward another.
-
B.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
C.
monotoneIn
Indicates that the relationship or function preserves a specified order when one of its arguments increases, meaning larger inputs (in that argument) do not lead to smaller outputs with respect to the given ordering.
-
D.
endsUp
Indicates that one entity ultimately arrives at, becomes, or results in another state, condition, or location after some process or sequence of events.
-
E.
hasAvarohana
Indicates a descending sequence or movement from higher to lower elements within a structured pattern or scale.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f42b11251881908070b93355de64ad |
completed | May 1, 2026, 4:24 a.m. |
Created at: April 18, 2026, 4:23 a.m.