Triple
T17982670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Una, Himachal Pradesh |
E449638
|
entity |
| Predicate | hasPlacesOfWorship |
P1191
|
FINISHED |
| Object | Hindu temples |
—
|
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: Hindu temples | Statement: [Una, Himachal Pradesh, hasPlacesOfWorship, Hindu temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlacesOfWorship Context triple: [Una, Himachal Pradesh, hasPlacesOfWorship, Hindu temples]
-
A.
hasPlaceOfWorship
chosen
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
-
B.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
C.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
D.
religiousBuildingCount
Indicates the number of religious buildings associated with or present in a given context or entity.
-
E.
religionBuildingDenomination
Indicates the specific religious denomination with which a religious building is affiliated or to which it belongs.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b297b7108190a676409b330ca23b |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.