Triple
T21017866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anandapala |
E517726
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Trilochanapala |
—
|
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: Trilochanapala | Statement: [Anandapala, successor, Trilochanapala]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Trilochanapala Context triple: [Anandapala, successor, Trilochanapala]
-
A.
Trilochanapala
chosen
Trilochanapala was the final ruler of the Hindu Shahi dynasty in northwestern India, known for his resistance against the early Ghaznavid invasions.
-
B.
Raghupala
Raghupala was a historical figure known primarily as the son of the Chaulukya (Solanki) king Mularaja of Gujarat.
-
C.
Gopala Champu
Gopala Champu is a classical Sanskrit poetic and prose composition by Jiva Goswami that narrates and glorifies the pastimes of Lord Krishna in an ornate, devotional style.
-
D.
Svayambhudeva
Svayambhudeva was a notable medieval Jain scholar and poet who composed influential works in the Apabhramsha language.
-
E.
Raghoba
Raghoba, also known as Raghunath Rao, was an 18th-century Maratha leader and briefly a claimant to the Peshwa title in the Maratha Empire.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5a27f08190b26828a6a7b59f7c |
completed | April 21, 2026, 4:26 a.m. |
Created at: April 16, 2026, 1:54 p.m.