Triple
T38356010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukteshwar Dham Temple |
E1046328
|
entity |
| Predicate | hasMainShrineOf |
P21389
|
FINISHED |
| Object | Shiva lingam |
E341647
|
NE 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: Shiva lingam | Statement: [Mukteshwar Dham Temple, hasMainShrineOf, Shiva lingam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainShrineOf Context triple: [Mukteshwar Dham Temple, hasMainShrineOf, Shiva lingam]
-
A.
isMostSacredShrineOf
Indicates that one entity is regarded as the holiest or most sacred shrine associated with another entity (such as a deity, religion, or tradition).
-
B.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
C.
countryShrineOf
Indicates that a country is the location or host nation of a particular shrine.
-
D.
hasMajorShrine
chosen
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
E.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
- F. None of above.
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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7fd71788190a4928633e49afa62 |
completed | June 28, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.