Triple
T5910084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Col |
E131436
|
entity |
| Predicate | positionOnEverest |
P44470
|
FINISHED |
| Object | north side of Mount Everest |
—
|
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: north side of Mount Everest | Statement: [North Col, positionOnEverest, north side of Mount Everest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnEverest Context triple: [North Col, positionOnEverest, north side of Mount Everest]
-
A.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
B.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
C.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
D.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
E.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.