Triple
T4512545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanda |
E102083
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Gokul |
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: Gokul | Statement: [Nanda, associatedWith, Gokul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gokul Context triple: [Nanda, associatedWith, Gokul]
-
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.
Chitrari
Chitrari is an alternative name for the Khowar language, an Indo-Aryan language spoken primarily in the Chitral region of northern Pakistan.
-
C.
Kalgidhar
Kalgidhar is an honorific epithet of Guru Gobind Singh, emphasizing his revered status as a timeless, divine protector in Sikh tradition.
-
D.
Mahodara
Mahodara is a revered form of the Hindu deity Ganesha, particularly associated with prosperity, generosity, and the fulfillment of devotees’ wishes.
-
E.
Dhundhari
Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5722d8fc81909c5f2d9a38d17a6b |
completed | March 20, 2026, 2:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bda42699648190a54e8c474766d29d |
completed | March 20, 2026, 7:46 p.m. |
Created at: March 20, 2026, 1:01 p.m.