Triple
T1317142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cave of Hira |
E28129
|
entity |
| Predicate | approxElevationAboveMecca |
P26939
|
FINISHED |
| Object | several hundred meters |
—
|
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: several hundred meters | Statement: [Cave of Hira, approxElevationAboveMecca, several hundred meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxElevationAboveMecca Context triple: [Cave of Hira, approxElevationAboveMecca, several hundred meters]
-
A.
hasMinaretHeightApprox
Indicates that an entity has a minaret whose height is approximately a specified value, allowing for some margin of imprecision.
-
B.
distanceFromEquator
Indicates how far a location is from the Earth's equator, typically measured as a geographic or angular distance.
-
C.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
D.
distanceFromJerusalem
Indicates the spatial distance between a given location and Jerusalem.
-
E.
positionInIslamicCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Islamic (Hijri) calendar.
- F. None of above. chosen
Provenance (4 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c175079481909077cf11ed72d6fa |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfc2134c81909cbaaa151d96e9a8 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:55 p.m.