Triple
T23511757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Aqmar Mosque |
E572442
|
entity |
| Predicate | interiorOrientation |
P40589
|
FINISHED |
| Object | aligned with qibla |
—
|
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: aligned with qibla | Statement: [Al-Aqmar Mosque, interiorOrientation, aligned with qibla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorOrientation Context triple: [Al-Aqmar Mosque, interiorOrientation, aligned with qibla]
-
A.
locationOrientation
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
B.
coneOrientation
Indicates the directional alignment or pointing direction of a cone relative to a reference frame or object.
-
C.
surfaceOrientation
chosen
Indicates the spatial orientation or facing direction of a surface relative to a reference frame or viewpoint.
-
D.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
-
E.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa7e99b081909620c4f951100023 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.