Triple
T7225001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabal al-Nour |
E150356
|
entity |
| Predicate | climbedPrimarilyFor |
P75711
|
FINISHED |
| Object | religious devotion |
—
|
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: religious devotion | Statement: [Jabal al-Nour, climbedPrimarilyFor, religious devotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbedPrimarilyFor Context triple: [Jabal al-Nour, climbedPrimarilyFor, religious devotion]
-
A.
usuallyClimbedAs
Indicates that an object, route, or feature is most commonly or traditionally ascended in a particular style, manner, or configuration.
-
B.
climbedWith
Indicates that one entity climbed together with another entity, sharing the ascent as a joint activity.
-
C.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
-
D.
climbingUse
Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
-
E.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9dc835881909ea646c392a980b6 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:54 p.m.