Triple
T32281180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jibal Tuwaiq |
E824692
|
entity |
| Predicate | hasLandformFeature |
P22129
|
FINISHED |
| Object | steep western face |
—
|
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: steep western face | Statement: [Jibal Tuwaiq, hasLandformFeature, steep western face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandformFeature Context triple: [Jibal Tuwaiq, hasLandformFeature, steep western face]
-
A.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
C.
hasLandformOrigin
Indicates that something originates from, or is formed by, a particular landform.
-
D.
hasLandscapeFeatures
chosen
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
E.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 12:43 a.m.