Triple
T4522740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yashoda |
E103305
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Gokula |
E105553
|
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: Gokula | Statement: [Yashoda, associatedWith, Gokula]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gokula Context triple: [Yashoda, associatedWith, Gokula]
-
A.
Gokul
chosen
Gokul is a historic town in Uttar Pradesh, India, revered in Hindu tradition as the place where Lord Krishna spent his early childhood.
-
B.
Kishkindha
Kishkindha is the mythical monkey kingdom ruled by Sugriva in the Indian epic Ramayana, where Rama forms an alliance with the vanara army to search for Sita.
-
C.
Kadamtala
Kadamtala is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
-
D.
Gajanana
Gajanana is a revered aspect of the Hindu deity Ganesha, emphasizing his elephant-faced form and role as the remover of obstacles and bestower of wisdom.
-
E.
Singhwara
Singhwara is a town located in the Darbhanga district of the Indian state of Bihar.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd574d7c2481909049955ca47613a6 |
completed | March 20, 2026, 2:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdb90b785c81909e76469819f3a487 |
completed | March 20, 2026, 9:15 p.m. |
Created at: March 20, 2026, 1:02 p.m.