Triple
T19897779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Princeton |
E478195
|
entity |
| Predicate | seasonalClimbing |
P1325
|
FINISHED |
| Object | commonly climbed in summer |
—
|
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: commonly climbed in summer | Statement: [Mount Princeton, seasonalClimbing, commonly climbed in summer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalClimbing Context triple: [Mount Princeton, seasonalClimbing, commonly climbed in summer]
-
A.
climbingSeason
chosen
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
B.
mountaineeringActivity
Indicates an activity where individuals engage in climbing or traversing mountains, often involving specialized skills and equipment.
-
C.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
D.
coClimber
Indicates that two or more entities participate together in the same climbing activity or ascent.
-
E.
climbingDiscipline
Indicates the specific style or category of climbing practiced or associated with an entity (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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593ef8dc8190be5b64988eceafac |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.