Triple
T27435091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wedge Glacier |
E690757
|
entity |
| Predicate | climbingAccessFrom |
P104061
|
FINISHED |
| Object | Wedge Creek area |
—
|
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: Wedge Creek area | Statement: [Wedge Glacier, climbingAccessFrom, Wedge Creek area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingAccessFrom Context triple: [Wedge Glacier, climbingAccessFrom, Wedge Creek area]
-
A.
climbingAccess
chosen
Indicates that one entity provides permission, routes, or means for another entity to engage in climbing activities at a particular location or structure.
-
B.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
C.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
D.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
-
E.
hasClimbFrom
Indicates a relationship where one location or object serves as the starting point from which a climb or ascent to another location or object begins.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 12:43 p.m.