Triple
T19373774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramachandra Pandurang Tope |
E484610
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Pandurang |
—
|
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: Pandurang | Statement: [Ramachandra Pandurang Tope, father, Pandurang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pandurang Context triple: [Ramachandra Pandurang Tope, father, Pandurang]
-
A.
Pandurang
chosen
Pandurang is the father of Ramachandra Pandurang Tope, better known as the Indian independence fighter Tatya Tope.
-
B.
Narasinga
Narasinga was a prominent monarch of the Vemulavada Chalukya dynasty in early medieval South India, known for consolidating regional power and patronizing Hindu temples and culture.
-
C.
Mahadeva
Mahadeva is a principal form of the Hindu god Shiva, revered as the supreme deity and great lord in Shaivism.
-
D.
Panduranga
Panduranga is a revered Hindu deity worshipped primarily in Maharashtra as a form of Vishnu or Krishna, especially associated with the temple town of Pandharpur.
-
E.
Panduranga
Panduranga was a historical Cham polity and important regional center located in what is now south-central Vietnam.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61a59f8cc8190b314cba95c25f2a0 |
completed | April 20, 2026, 12:21 p.m. |
Created at: April 10, 2026, 1:35 p.m.