Triple
T26690711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Mount Everest Expedition 1952 |
E672872
|
entity |
| Predicate | routeAttempted |
P161118
|
FINISHED |
| Object | South Col route |
—
|
NE NERFINISHED |
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: South Col route | Statement: [Swiss Mount Everest Expedition 1952, routeAttempted, South Col route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeAttempted Context triple: [Swiss Mount Everest Expedition 1952, routeAttempted, South Col route]
-
A.
routeAffected
Indicates that a transportation route is impacted or disrupted in some way, such as by delays, closures, or changes in service.
-
B.
routeTypeAccessed
Indicates that a particular type of route has been accessed or used in some context.
-
C.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
D.
routeTargeted
Indicates that a route is specifically directed toward or intended to reach a particular target entity or destination.
-
E.
routeDiscovered
Indicates that a path or connection between two locations or nodes has been successfully found or identified.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617424a9881909cdec90173560455 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 3:25 a.m.