Triple
T4903393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte San Clemente |
E109854
|
entity |
| Predicate | hasClimbingHazards |
P10757
|
FINISHED |
| Object | crevasses |
—
|
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: crevasses | Statement: [Monte San Clemente, hasClimbingHazards, crevasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingHazards Context triple: [Monte San Clemente, hasClimbingHazards, crevasses]
-
A.
hasClimbingHazard
chosen
Indicates that something presents a risk or danger specifically associated with climbing activities.
-
B.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
C.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
D.
hasClimbSide
Indicates that one entity has a particular side or surface that is suitable or designated for climbing.
-
E.
hasCliff
Indicates that something possesses or features a steep, high rock face or abrupt vertical drop as part of its structure or environment.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:28 p.m.