Triple
T1988462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Stone corner |
E43194
|
entity |
| Predicate | directionOfMovement |
P16306
|
FINISHED |
| Object | counterclockwise around the Kaaba |
—
|
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: counterclockwise around the Kaaba | Statement: [Black Stone corner, directionOfMovement, counterclockwise around the Kaaba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfMovement Context triple: [Black Stone corner, directionOfMovement, counterclockwise around the Kaaba]
-
A.
movementDirection
chosen
Indicates the direction or path along which an entity moves or is moving relative to a reference frame or point.
-
B.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
C.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8ee02dc81908fec9fd8df7a4f40 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb79ad6888190be99943a9c73cf3e |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.