Triple
T16531788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windy Corner |
E401583
|
entity |
| Predicate | typicallyCrossedOn |
P18953
|
FINISHED |
| Object | summit push progression toward 14,000-foot camp |
—
|
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: summit push progression toward 14,000-foot camp | Statement: [Windy Corner, typicallyCrossedOn, summit push progression toward 14,000-foot camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyCrossedOn Context triple: [Windy Corner, typicallyCrossedOn, summit push progression toward 14,000-foot camp]
-
A.
oftenCrossedOn
chosen
Indicates that one entity is frequently traversed or passed over by another entity.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
-
E.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed8075c81908ff47396879abd0c |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.