Triple
T18809520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Meyer Peak |
E459969
|
entity |
| Predicate | relativePositionOnMawenzi |
P105158
|
FINISHED |
| Object | highest eastern 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: highest eastern summit | Statement: [Hans Meyer Peak, relativePositionOnMawenzi, highest eastern summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionOnMawenzi Context triple: [Hans Meyer Peak, relativePositionOnMawenzi, highest eastern summit]
-
A.
relativeLocationToMakalu
Indicates the spatial relationship of an entity’s location with respect to the position of Makalu.
-
B.
positionRelativeToSummit
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
C.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
D.
distanceToAmboseliNationalPark
Indicates the measured or estimated spatial distance between a given entity and Amboseli National Park.
-
E.
relativePositioning
chosen
Indicates how one entity is spatially arranged or located in relation to another entity.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3db38ec8190ab5bef15bc6789be |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.