Triple
T33695634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Climb area of Mount Adams |
E863299
|
entity |
| Predicate | hasHighCampArea |
P180856
|
FINISHED |
| Object | Lunch Counter |
—
|
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: Lunch Counter | Statement: [South Climb area of Mount Adams, hasHighCampArea, Lunch Counter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighCampArea Context triple: [South Climb area of Mount Adams, hasHighCampArea, Lunch Counter]
-
A.
hasHighCampOn
Indicates that one entity maintains or has established a primary or elevated campsite located on another entity (typically a mountain or route).
-
B.
hasHigherElevationArea
Indicates that one area is situated at a greater elevation above sea level than another area.
-
C.
higherCamp
Indicates that one camp is located at a higher elevation or position relative to another camp.
-
D.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
E.
hasMountaineeringArea
chosen
Indicates that an entity is associated with or contains a designated area suitable for mountaineering activities.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:43 a.m.