Triple
T4519454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanuman Temple (Connaught Place) |
E103229
|
entity |
| Predicate | governingReligion |
P45
|
FINISHED |
| Object | Sanatana Dharma |
—
|
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: Sanatana Dharma | Statement: [Hanuman Temple (Connaught Place), governingReligion, Sanatana Dharma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingReligion Context triple: [Hanuman Temple (Connaught Place), governingReligion, Sanatana Dharma]
-
A.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
B.
dominantReligion
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
C.
dominantReligionPolicy
Indicates the policy or stance an authority adopts toward the religion that holds dominant or majority status within a given context.
-
D.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
E.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
- 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_69bd43dba59881908cf59b31df8c7ae1 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5747e90c81908fa112ecace699a9 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.