Triple
T27401038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gray Peak |
E691841
|
entity |
| Predicate | climbingObjectiveFor |
P75711
|
FINISHED |
| Object | Adirondack 46ers |
—
|
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: Adirondack 46ers | Statement: [Gray Peak, climbingObjectiveFor, Adirondack 46ers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingObjectiveFor Context triple: [Gray Peak, climbingObjectiveFor, Adirondack 46ers]
-
A.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
-
B.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
C.
climbingUse
Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
-
D.
climbedPrimarilyFor
chosen
Indicates that the primary purpose or motivation for someone climbing something was for the specified reason or goal.
-
E.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 12:29 p.m.