Triple
T18555980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganesha Ratha |
E453503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pallava-era monument |
C40606
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Pallava-era monument Context triple: [Ganesha Ratha, instanceOf, Pallava-era monument]
-
A.
Mughal-era monument
A Mughal-era monument is a historic architectural structure built during the Mughal Empire, typically characterized by grand scale, intricate ornamentation, symmetrical design, and a blend of Persian, Islamic, and Indian styles.
-
B.
Majapahit-era monument
A Majapahit-era monument is a historical structure or site originating from the Majapahit Kingdom (circa 13th–16th centuries) that reflects its distinctive architectural style, religious syncretism, and political or cultural significance in maritime Southeast Asia.
-
C.
Majapahit-era structure
A Majapahit-era structure is an architectural construct from the 13th–16th century Majapahit Empire in Java, characterized by red-brick construction, terraced forms, intricate reliefs, and a blend of Hindu-Buddhist and indigenous Javanese design elements.
-
D.
South Indian royal dynasty
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, culture, religion, and art over successive generations.
-
E.
South Indian dynasty
A South Indian dynasty is a long-standing ruling lineage or family that governed regions of southern India, shaping its political history, culture, religion, and art over successive generations.
- F. None of above. chosen
Provenance (1 batch)
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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:38 a.m.