Triple
T27418669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kautz Glacier |
E692974
|
entity |
| Predicate | isClimbedToReach |
P162395
|
FINISHED |
| Object | summit of Mount Rainier |
—
|
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: summit of Mount Rainier | Statement: [Kautz Glacier, isClimbedToReach, summit of Mount Rainier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isClimbedToReach Context triple: [Kautz Glacier, isClimbedToReach, summit of Mount Rainier]
-
A.
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.
-
B.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
C.
isClimbedIn
Indicates that an entity (typically a person or animal) ascends or climbs while being located within or inside another entity (such as a structure, vehicle, or environment).
-
D.
hasStaircaseToSummit
Indicates that there exists a staircase providing a direct route or access from a lower point to the summit of something.
-
E.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
- 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_69ef5208617081908f731d312e0fd1bc |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d1c589081909aca632309015c68 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 12:35 p.m.