Triple
T29393246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branscomb Glacier route |
E745426
|
entity |
| Predicate | standardAscentOf |
P37604
|
FINISHED |
| Object | Vinson Massif |
—
|
NE NERFINISHED |
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: Vinson Massif | Statement: [Branscomb Glacier route, standardAscentOf, Vinson Massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardAscentOf Context triple: [Branscomb Glacier route, standardAscentOf, Vinson Massif]
-
A.
typicalAscentStyle
Indicates the usual or characteristic manner or technique by which an ascent or climb is performed.
-
B.
typicalAscentCombinedWith
Indicates that one ascent or climbing route is normally undertaken together with another as part of a standard or customary combined itinerary.
-
C.
powersAscentOf
Indicates that one entity provides the driving force, energy, or enabling influence behind another entity’s rise, advancement, or upward progression.
-
D.
typicalAscentStartPoint
chosen
Indicates the usual or most common location from which an ascent or climb is begun.
-
E.
approximateAscent
Indicates an estimated or non-exact upward change or increase in value, level, or position.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 2:44 p.m.