Triple
T6430297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillary Step |
E128161
|
entity |
| Predicate | routeAssociation |
P5619
|
FINISHED |
| Object | Southeast Ridge route 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: Southeast Ridge route of Mount Everest | Statement: [Hillary Step, routeAssociation, Southeast Ridge route of Mount Everest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAssociation Context triple: [Hillary Step, routeAssociation, Southeast Ridge route of Mount Everest]
-
A.
routeRole
Indicates the specific functional role or purpose that an entity has within a particular route or path.
-
B.
route
chosen
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
C.
associatedWithRouteNetwork
Indicates a relationship where something is linked or connected to a specific route network.
-
D.
routeExtension
Indicates that an existing route is extended beyond its original endpoint to cover additional segments or destinations.
-
E.
routeSetting
Indicates that one entity configures or defines the path or course to be followed by another entity (such as a vehicle, signal, or data flow).
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0693b872c819082a7d0e257018831 |
completed | March 22, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:44 p.m.