Triple
T37087344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amer |
E918324
|
entity |
| Predicate | primaryReligionSites |
P34373
|
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: [Amer, primaryReligionSites, Hindu temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReligionSites Context triple: [Amer, primaryReligionSites, Hindu temples]
-
A.
religiousSiteInRegion
Indicates that a religious site is located within or belongs to a specified geographic region.
-
B.
traditionalReligionPlace
Indicates that a place is traditionally associated with the practice, worship, or activities of a particular religion.
-
C.
religiousSiteRank
Indicates the hierarchical or status-based rank assigned to a religious site within a religious or organizational structure.
-
D.
religiousSiteType
chosen
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
E.
religiousAffiliationOfMajorSite
Indicates the religion or denomination with which a major site (such as a temple, church, mosque, or shrine) is formally associated.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.