Triple
T30819142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mataf |
E784867
|
entity |
| Predicate | hasRitualStartPoint |
P177140
|
FINISHED |
| Object | Black Stone corner of the Kaaba |
—
|
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: Black Stone corner of the Kaaba | Statement: [Mataf, hasRitualStartPoint, Black Stone corner of the Kaaba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualStartPoint Context triple: [Mataf, hasRitualStartPoint, Black Stone corner of the Kaaba]
-
A.
hasRitualSpace
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
-
B.
hasRitualSequence
Indicates that one ritual is ordered to occur before or after another within a defined ceremonial sequence.
-
C.
hasRitualStage
Indicates that something is associated with, or occurs during, a particular stage within a ritual process.
-
D.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
E.
hasRitualSetting
chosen
Indicates that an entity is associated with a specific ritual context or environment in which it is performed, observed, or situated.
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:44 p.m.