Triple
T2984709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Icefield |
E80593
|
entity |
| Predicate | positionRelativeToSummit |
P44470
|
FINISHED |
| Object | near summit |
—
|
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: near summit | Statement: [Southern Icefield, positionRelativeToSummit, near summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToSummit Context triple: [Southern Icefield, positionRelativeToSummit, near summit]
-
A.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
B.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
C.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
D.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
E.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c65ad0819087bb4ae92ab0dc55 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:59 p.m.