Triple
T19484423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandikeshvara |
E487472
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Nandikeshvara Nandi |
—
|
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: Nandikeshvara Nandi | Statement: [Nandikeshvara, alsoKnownAs, Nandikeshvara Nandi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nandikeshvara Nandi Context triple: [Nandikeshvara, alsoKnownAs, Nandikeshvara Nandi]
-
A.
Nandikeshvara
chosen
Nandikeshvara is a revered figure in Hindu tradition, often identified with Nandi, the divine bull and devoted gatekeeper and attendant of the god Shiva.
-
B.
Vighneshvara
Vighneshvara is a prominent form of the Hindu god Ganesha, revered as the remover of obstacles and patron of beginnings and wisdom.
-
C.
Pandurang
Pandurang is the father of Ramachandra Pandurang Tope, better known as the Indian independence fighter Tatya Tope.
-
D.
Mahadeva
Mahadeva is a principal form of the Hindu god Shiva, revered as the supreme deity and great lord in Shaivism.
-
E.
Purandara Bhairava
Purandara Bhairava is a deity or legendary figure in Hindu tradition after whom the historic Purandar Fort in Maharashtra, India, is named.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343dcc748190b0df816e6ab4cafb |
completed | April 20, 2026, 2:12 p.m. |
Created at: April 10, 2026, 1:39 p.m.