Triple
T17936982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harsha |
E448492
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Prabhakaravardhana |
—
|
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: Prabhakaravardhana | Statement: [Harsha, father, Prabhakaravardhana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prabhakaravardhana Context triple: [Harsha, father, Prabhakaravardhana]
-
A.
Prabhakaravardhana
chosen
Prabhakaravardhana was an early 7th-century Indian king of the Pushyabhuti (Vardhana) dynasty and father of the renowned emperor Harsha.
-
B.
Durlabhavardhana
Durlabhavardhana was an early medieval ruler of Kashmir who established the influential Karkota dynasty that dominated the region for several centuries.
-
C.
Devapala
Devapala was a powerful 9th-century ruler of the Pala dynasty in eastern India, known for expanding the empire to its greatest territorial extent and patronizing Buddhism.
-
D.
Devagupta
Devagupta was a monarch of the Later Gupta dynasty, a post-Gupta ruling house in northern India.
-
E.
Durlabharaja
Durlabharaja was a medieval Indian ruler, likely a Chaulukya (Solanki) prince or king of Gujarat, known from inscriptions and genealogies of the dynasty.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad924f6c8190a0d676dfa20c9918 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 10:21 a.m.