Triple
T6940854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uhud Martyrs Cemetery |
E160667
|
entity |
| Predicate | proximityToHaram |
P61362
|
FINISHED |
| Object | outside the Prophet's Mosque sanctuary area |
—
|
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: outside the Prophet's Mosque sanctuary area | Statement: [Uhud Martyrs Cemetery, proximityToHaram, outside the Prophet's Mosque sanctuary area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToHaram Context triple: [Uhud Martyrs Cemetery, proximityToHaram, outside the Prophet's Mosque sanctuary area]
-
A.
religiousRestriction
Indicates that one entity imposes, experiences, or is subject to limitations or rules based on religious beliefs or practices in relation to another entity or context.
-
B.
distanceFromMhamid
Indicates the spatial distance between an entity and the reference location Mhamid.
-
C.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
D.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
-
E.
occursNear
Indicates that one event or entity takes place or exists in close spatial proximity to another.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.