Triple
T19721280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nityananda |
E473614
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Navadvipa |
—
|
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: Navadvipa | Statement: [Nityananda, associatedWith, Navadvipa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Navadvipa Context triple: [Nityananda, associatedWith, Navadvipa]
-
A.
Navadvipa
chosen
Navadvipa is a historic town in West Bengal, India, revered as a major center of Gaudiya Vaishnavism and the birthplace region of the saint Chaitanya Mahaprabhu.
-
B.
Manidvipa
Manidvipa is the supreme, jewel-like spiritual realm in Shakta tradition, revered as the transcendent cosmic seat of the goddess Lalita Tripurasundari.
-
C.
Pavapuri
Pavapuri is a revered Jain pilgrimage site in Bihar, India, best known as the place where Mahavira, the 24th Tirthankara, attained nirvana.
-
D.
Nagaloka
Nagaloka is the mythological subterranean realm in Hindu and Buddhist cosmology that serves as the domain of serpentine beings known as nagas.
-
E.
Haladhara
Haladhara is another name for the Hindu deity Balarama, revered as Krishna’s elder brother and famed for wielding the plough as his primary weapon.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f483c481908c6b3114bf9c5934 |
completed | April 20, 2026, 3:44 p.m. |
Created at: April 10, 2026, 1:46 p.m.