Triple
T12847495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rana Kumbha |
E307217
|
entity |
| Predicate | VijayStambhaPurpose |
P107199
|
FINISHED |
| Object | commemoration of victory over Malwa |
—
|
LITERAL 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: commemoration of victory over Malwa | Statement: [Rana Kumbha, VijayStambhaPurpose, commemoration of victory over Malwa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VijayStambhaPurpose Context triple: [Rana Kumbha, VijayStambhaPurpose, commemoration of victory over Malwa]
-
A.
hasTemplePurpose
Indicates that something (such as a building, site, or structure) is intended, used, or designated for temple-related purposes or functions.
-
B.
numberOfGopurams
Indicates the specific count of gopurams (temple gateway towers) associated with an entity.
-
C.
hasGopuramsCountApprox
Indicates an approximate number of gopurams (temple towers) associated with an entity.
-
D.
gandhiVisitPurpose
Indicates the purpose or reason for Gandhi’s visit in the described context.
-
E.
VajranabhaIs
Indicates that something or someone is identified as or characterized by being Vajranabha.
- F. None of above. chosen
Provenance (4 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:36 p.m.