Triple
T24747928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raga Kafi |
E619053
|
entity |
| Predicate | hasThaatPosition |
P157089
|
FINISHED |
| Object | third thaat in Bhatkhande system |
—
|
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: third thaat in Bhatkhande system | Statement: [Raga Kafi, hasThaatPosition, third thaat in Bhatkhande system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThaatPosition Context triple: [Raga Kafi, hasThaatPosition, third thaat in Bhatkhande system]
-
A.
hasPositionOn
Indicates that one entity occupies or holds a specific role, job, or spatial location relative to another entity.
-
B.
hasPositionInPaksha
Indicates that an entity holds a specific role or position within a particular Paksha (faction, side, or group).
-
C.
hasDancePosition
Indicates that one entity occupies or is assigned a specific position or role within a dance formation or choreography.
-
D.
hasTowerPosition
Indicates that an entity occupies or is assigned a specific position or location within a tower.
-
E.
thaat
Indicates a relationship where one entity is the target, recipient, or endpoint toward which another entity or action is directed.
- 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_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:23 a.m.