Triple
T19594726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raghuvamsha |
E470321
|
entity |
| Predicate | notableMember |
P10
|
FINISHED |
| Object | Raghu |
—
|
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: Raghu | Statement: [Raghuvamsha, notableMember, Raghu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raghu Context triple: [Raghuvamsha, notableMember, Raghu]
-
A.
Raghu
chosen
Raghu was a monarch of the ancient Indian Kadamba dynasty, known for ruling parts of present-day Karnataka.
-
B.
Raghava
Raghava is an epithet of the Hindu deity Rama, highlighting his lineage from the Raghu dynasty and his role as a central hero of the Ramayana.
-
C.
Rajan
Rajan is an ancient Indian royal title denoting a king or ruler, commonly used in early historic dynasties such as the Satavahanas.
-
D.
Ravi
Ravi is a common Indian male given name of Sanskrit origin meaning "sun" or "sun god."
-
E.
Ravi
Ravi is one of the major rivers of northern India and Pakistan, flowing through the Punjab region and serving as an important tributary of the Indus River system.
- 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_69e640793cd88190b9b84491bfb2493f |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.