Triple
T16417892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gopal Ganesh Agarkar |
E398736
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gopal |
E143849
|
NE FINISHED |
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: Gopal | Statement: [Gopal Ganesh Agarkar, givenName, Gopal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gopal Context triple: [Gopal Ganesh Agarkar, givenName, Gopal]
-
A.
Gopal
chosen
Gopal is the given name of Gopal Krishna Gokhale, a prominent Indian political leader and social reformer of the early 20th century.
-
B.
Govind
Govind is a Hindu deity, commonly identified with Lord Krishna or Vishnu, who is venerated as the divine protector and guide of devotees.
-
C.
Ghanshyam
Ghanshyam is the given name of Ghanshyam Das Birla, a prominent Indian industrialist and philanthropist of the 20th century.
-
D.
Gangadhar
Gangadhar is the given name of Raja Gangadhar Rao, a 19th-century Maratha ruler of the princely state of Jhansi in India.
-
E.
Gopala
Gopala is a pastoral form of the Hindu god Krishna, revered especially as a divine cowherd and protector of cows.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328798a488190a5fad01c3c95584c |
completed | April 18, 2026, 6:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c6ca1bc8190a6c4f675ec8e3a53 |
completed | May 10, 2026, 8:06 a.m. |
Created at: April 10, 2026, 5:09 a.m.