Triple
T35435873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maan Mandir |
E1024202
|
entity |
| Predicate | locatedInReligiousRegion |
P135153
|
FINISHED |
| Object | Braj Bhoomi |
E63432
|
NE 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: Braj Bhoomi | Statement: [Maan Mandir, locatedInReligiousRegion, Braj Bhoomi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInReligiousRegion Context triple: [Maan Mandir, locatedInReligiousRegion, Braj Bhoomi]
-
A.
laterReligionRegionOf
Indicates that a region became associated with a particular religion at a later time than another referenced region or context.
-
B.
locatedInEcclesiasticalRegion
Indicates that one entity is situated within or falls under the jurisdiction of a particular ecclesiastical (church-governed) region.
-
C.
religionInRegion
Indicates that a particular religion is practiced or present within a specified geographic region.
-
D.
regionOfReligiousSignificance
chosen
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
-
E.
religionSignificantMinorityRegion
Indicates that a particular religion constitutes a significant minority presence within a specified geographic region.
- F. None of above.
Provenance (4 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a384029b4cc819083a6a873f8512ec7 |
completed | June 21, 2026, 7:48 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.