Triple
T19168453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitragupta Temple |
E469248
|
entity |
| Predicate | architecturalStyle |
P607
|
FINISHED |
| Object | Nagara |
—
|
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: Nagara | Statement: [Chitragupta Temple, architecturalStyle, Nagara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nagara Context triple: [Chitragupta Temple, architecturalStyle, Nagara]
-
A.
Nagara
chosen
Nagara is a traditional North Indian temple architectural style characterized by its beehive-shaped tower (shikhara) and intricate stone carvings.
-
B.
Nagara Khanda
Nagara Khanda is a major section of the Skanda Purana that focuses on sacred cities, their legends, and associated religious practices in Hindu tradition.
-
C.
Mahodara
Mahodara is a revered form of the Hindu deity Ganesha, particularly associated with prosperity, generosity, and the fulfillment of devotees’ wishes.
-
D.
Kanheya
Kanheya is the surname of Jai Singh Kanheya, associated with a historical family or lineage.
-
E.
Gaurahari
Gaurahari is an alternative name for Nimai, a devotional epithet associated with the Hindu saint and avatar Chaitanya Mahaprabhu.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16132e081908c6b8d576163316e |
completed | April 20, 2026, 9:26 a.m. |
Created at: April 10, 2026, 12:06 p.m.