Triple
T19595450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kusha |
E470336
|
entity |
| Predicate | ethnicGroup |
P194
|
FINISHED |
| Object | Raghuvamsha |
—
|
NE NERFINISHED |
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: Raghuvamsha | Statement: [Kusha, ethnicGroup, Raghuvamsha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raghuvamsha Context triple: [Kusha, ethnicGroup, Raghuvamsha]
-
A.
Raghuvamsha
chosen
Raghuvamsha is the legendary royal lineage in Indian epic tradition to which the hero-king Bharata belongs, celebrated in classical Sanskrit literature and mythology.
-
B.
Harischandra Upakhyan
Harischandra Upakhyan is a devotional literary work in the Assamese Vaishnavite tradition, authored by the saint-scholar Srimanta Sankardev.
-
C.
Markandeya
Markandeya is a revered sage in Hindu tradition, famed for his extraordinary longevity, devotion to Shiva, and visionary accounts of cosmic cycles and deluges.
-
D.
Somavamsa
Somavamsa is a legendary royal lineage in ancient Indian tradition believed to descend from the moon god Chandra.
-
E.
Harivamsa
Harivamsa is an important Sanskrit text traditionally considered an appendix to the Mahabharata, detailing the genealogy, birth, and early life of Krishna.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407a09608190aa1df92f8c21f9e7 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.