Triple
T6541120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaweah Peaks Ridge |
E168288
|
entity |
| Predicate | firstAscentEra |
P41404
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Kaweah Peaks Ridge, firstAscentEra, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentEra Context triple: [Kaweah Peaks Ridge, firstAscentEra, late 19th century]
-
A.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
B.
firstMajorAscentsPeriod
chosen
Indicates the time period during which the first major ascents or significant climbs of a mountain or route took place.
-
C.
firstFreeAscentYear
Indicates the year in which the first successful free ascent of a route or peak was completed.
-
D.
firstAscentYear
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
E.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
- 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_69c68a51564081909e93aee0dbd9cca3 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.