Triple
T20096086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidimba Devi Temple |
E496403
|
entity |
| Predicate | hasSanctumFeature |
P182
|
FINISHED |
| Object | footprints of Hidimba Devi |
—
|
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: footprints of Hidimba Devi | Statement: [Hidimba Devi Temple, hasSanctumFeature, footprints of Hidimba Devi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSanctumFeature Context triple: [Hidimba Devi Temple, hasSanctumFeature, footprints of Hidimba Devi]
-
A.
hasSanctumImage
Indicates that an entity is associated with a specific image representing its sanctum or sacred/private space.
-
B.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
C.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
hasFeatureStatus
Indicates that an entity possesses a particular feature along with its current state or condition.
-
E.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6666cc02481908780a415b19c05a2 |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:25 p.m.