Triple
T2078130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judean Mountains |
E44975
|
entity |
| Predicate | elevationOfJerusalem |
P221
|
FINISHED |
| Object | approximately 650–840 m |
—
|
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: approximately 650–840 m | Statement: [Judean Mountains, elevationOfJerusalem, approximately 650–840 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevationOfJerusalem Context triple: [Judean Mountains, elevationOfJerusalem, approximately 650–840 m]
-
A.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
B.
distanceFromJerusalem
Indicates the spatial distance between a given location and Jerusalem.
-
C.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
elevationContext
Indicates the contextual relationship between an entity and its elevation or vertical position relative to a reference point or environment.
-
E.
approxElevationAboveMecca
Indicates that one location’s elevation is approximately a specified amount higher or lower than the elevation of Mecca.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba31eef8819081cf7f5334b59fe1 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.