Triple
T9099207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarvepalli Gopal |
E218107
|
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: [Sarvepalli Gopal, givenName, Gopal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gopal Context triple: [Sarvepalli Gopal, 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.
Ghanshyam
Ghanshyam is the given name of Ghanshyam Das Birla, a prominent Indian industrialist and philanthropist of the 20th century.
-
C.
Gopala
Gopala is a pastoral form of the Hindu god Krishna, revered especially as a divine cowherd and protector of cows.
-
D.
Shyam
Shyam is the young protagonist of the classic Marathi autobiographical novel "Shyamchi Aai," depicting his deep bond with his mother and his moral and emotional growth.
-
E.
Rajagopala
Rajagopala is a Hindu deity regarded as a form of Lord Krishna, particularly venerated as the divine cowherd and king of Gokul.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9710ac04819096b9c8d3399b9c35 |
completed | April 1, 2026, 3:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d01824ee2081909cc5e6ae33fab2e5 |
completed | April 3, 2026, 7:42 p.m. |
Created at: March 30, 2026, 7:15 p.m.