Triple
T27070147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahobilam Narasimha temples |
E685300
|
entity |
| Predicate | featuresShrine |
P27591
|
FINISHED |
| Object | Jwala Narasimha |
—
|
NE NERFINISHED |
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: Jwala Narasimha | Statement: [Ahobilam Narasimha temples, featuresShrine, Jwala Narasimha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresShrine Context triple: [Ahobilam Narasimha temples, featuresShrine, Jwala Narasimha]
-
A.
typicalShrineFeature
chosen
Indicates that something is a characteristic or commonly found element of a shrine.
-
B.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
C.
shrineSignificance
Indicates the cultural, religious, or historical importance attributed to a particular shrine within its context.
-
D.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
E.
recognizedAsShrineBy
Indicates that something is regarded or designated as a shrine by a particular person, group, or authority.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 27, 2026, 8:27 a.m.