Triple
T30819170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safā and Marwah area |
E784868
|
entity |
| Predicate | ritualStartPoint |
P170541
|
FINISHED |
| Object | Safa |
—
|
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: Safa | Statement: [Safā and Marwah area, ritualStartPoint, Safa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualStartPoint Context triple: [Safā and Marwah area, ritualStartPoint, Safa]
-
A.
initiatesRitual
Indicates that one entity begins or sets in motion a ritual involving one or more other entities.
-
B.
positionOnRitual
Indicates the stance, role, or placement an entity holds with respect to a particular ritual or ceremonial practice.
-
C.
ritualCentersOn
Indicates that a ritual is primarily focused on, organized around, or thematically centered on a particular entity, object, or concept.
-
D.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
-
E.
ritualMovementBetween
chosen
Indicates a movement performed as part of a ritual that transitions or passes between two locations, participants, or ritual elements.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:44 p.m.