Triple
T19329632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maihar |
E483450
|
entity |
| Predicate | hasHillTemple |
P95312
|
FINISHED |
| Object | Maa Sharda Devi temple on Trikuta hill |
—
|
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: Maa Sharda Devi temple on Trikuta hill | Statement: [Maihar, hasHillTemple, Maa Sharda Devi temple on Trikuta hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHillTemple Context triple: [Maihar, hasHillTemple, Maa Sharda Devi temple on Trikuta hill]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hillTemple
chosen
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
-
C.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
D.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
E.
hasHistoricTemple
Indicates that an entity possesses, contains, or is associated with a temple of historical significance.
- F. None of above.
Provenance (3 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6163ffddc81909e9cb13e780f1f18 |
completed | April 20, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:33 p.m.