Triple
T31961195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Mash'ar al-Haram |
E816043
|
entity |
| Predicate | connectedRituallyTo |
P57110
|
FINISHED |
| Object | Arafat |
—
|
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: Arafat | Statement: [Al-Mash'ar al-Haram, connectedRituallyTo, Arafat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedRituallyTo Context triple: [Al-Mash'ar al-Haram, connectedRituallyTo, Arafat]
-
A.
associatedWithSacrament
Indicates a relationship where something is connected or related to a specific sacrament in a religious or ritual context.
-
B.
usesRitually
Indicates that an entity employs or performs something as part of a ritual or ceremonial practice.
-
C.
hasLiturgicalRelationTo
Indicates a relationship in which one entity is connected to another through liturgical roles, functions, practices, or contexts within religious worship.
-
D.
relatedRitual
chosen
Indicates that one entity is associated with, connected to, or involved in the performance or context of a particular ritual.
-
E.
followsRitualTraditionOf
Indicates that one entity practices, observes, or adheres to the ritual traditions established or maintained by another entity.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 12:09 a.m.