Triple
T16531785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windy Corner |
E401583
|
entity |
| Predicate | nearCamp |
P79315
|
FINISHED |
| Object | Camp 3 at 11000 feet on West Buttress |
—
|
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: Camp 3 at 11000 feet on West Buttress | Statement: [Windy Corner, nearCamp, Camp 3 at 11000 feet on West Buttress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearCamp Context triple: [Windy Corner, nearCamp, Camp 3 at 11000 feet on West Buttress]
-
A.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
B.
nearbyCampground
chosen
Indicates that one location has a campground situated close to it in geographic proximity.
-
C.
nearRetailPark
Indicates that one entity is located close to or in the immediate vicinity of a retail park.
-
D.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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.