Triple
T36574914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larke Peak |
E902218
|
entity |
| Predicate | approachPass |
P200422
|
FINISHED |
| Object | Larkya La pass |
—
|
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: Larkya La pass | Statement: [Larke Peak, approachPass, Larkya La pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachPass Context triple: [Larke Peak, approachPass, Larkya La pass]
-
A.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than it.
-
B.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
C.
guardedApproachTo
Indicates a cautious, defensive, or wary manner of moving toward or engaging with another entity.
-
D.
followsPass
Indicates that one entity moves behind or in the path of another entity who has just passed, maintaining a trailing or subsequent position.
-
E.
approachControl
Indicates that one entity moves closer to another entity in a deliberate or controlled manner.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
| PDg | Predicate description generation | batch_69ff891d54248190be8742197564605a |
completed | May 9, 2026, 7:21 p.m. |
Created at: May 3, 2026, 4:11 p.m.