Triple
T35105650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tocllaraju |
E1013144
|
entity |
| Predicate | hasClassicRoute |
P4374
|
FINISHED |
| Object | Northwest ridge |
—
|
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: Northwest ridge | Statement: [Tocllaraju, hasClassicRoute, Northwest ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClassicRoute Context triple: [Tocllaraju, hasClassicRoute, Northwest ridge]
-
A.
hasClassicRide
Indicates that an entity possesses or is associated with a traditional or iconic ride or vehicle.
-
B.
hasClassicResult
Indicates that an entity is associated with a canonical, established, or traditionally recognized result or outcome.
-
C.
hasClassicRace
Indicates that an entity is associated with, participates in, or features a traditional or historically established race event.
-
D.
hasRoute
chosen
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
E.
hasCommonRoute
Indicates that two or more entities share at least one overlapping or identical route or path.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:01 p.m.