Triple
T25239200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mewat |
E632416
|
entity |
| Predicate | religiousSiteInRegion |
P167710
|
FINISHED |
| Object | Shrine of Sheikh Musa |
—
|
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: Shrine of Sheikh Musa | Statement: [Mewat, religiousSiteInRegion, Shrine of Sheikh Musa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousSiteInRegion Context triple: [Mewat, religiousSiteInRegion, Shrine of Sheikh Musa]
-
A.
regionOfReligiousSignificance
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
-
B.
religiousSiteType
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
C.
religiousSiteRank
Indicates the hierarchical or status-based rank assigned to a religious site within a religious or organizational structure.
-
D.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
E.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
- F. None of above. chosen
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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 21, 2026, 1:07 p.m.