Triple
T23342913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NorthColRoute |
E591780
|
entity |
| Predicate | reachesSummitFrom |
P75551
|
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: [NorthColRoute, reachesSummitFrom, north side of Mount Everest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachesSummitFrom Context triple: [NorthColRoute, reachesSummitFrom, north side of Mount Everest]
-
A.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
B.
reachesSummitOf
chosen
Indicates that one entity successfully arrives at or attains the highest point or summit of another entity.
-
C.
reachedSummitWith
Indicates that one entity arrived at or attained the summit together with another entity, as part of the same ascent or achievement.
-
D.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
-
E.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983431f08190b0078728d44872a8 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.