Triple
T37838616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omkar Mandhata temple |
E943406
|
entity |
| Predicate | numberInJyotirlingas |
P46565
|
FINISHED |
| Object | one of the twelve Jyotirlingas |
—
|
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: one of the twelve Jyotirlingas | Statement: [Omkar Mandhata temple, numberInJyotirlingas, one of the twelve Jyotirlingas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInJyotirlingas Context triple: [Omkar Mandhata temple, numberInJyotirlingas, one of the twelve Jyotirlingas]
-
A.
hasNumberOfJyotirlingas
Indicates the relationship specifying how many Jyotirlingas (sacred Shiva shrines) are associated with a given entity.
-
B.
hasJyotirlingaStatus
chosen
Indicates that something holds the religious designation or status of a Jyotirlinga within the context of Hindu worship.
-
C.
hasNumberOfDivyaDesams
Indicates the specific count of Divya Desams associated with a given entity.
-
D.
numberOfGopurams
Indicates the specific count of gopurams (temple gateway towers) associated with an entity.
-
E.
numberOfJainCaves
Indicates the quantity of caves associated with Jainism that are present at or within a given entity or site.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.