Triple
T3142117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Pico |
E65673
|
entity |
| Predicate | hasFirstRecordedAscent |
P45620
|
FINISHED |
| Object | 1652 |
—
|
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: 1652 | Statement: [Mount Pico, hasFirstRecordedAscent, 1652]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstRecordedAscent Context triple: [Mount Pico, hasFirstRecordedAscent, 1652]
-
A.
firstOneDayAscentBy
Indicates that the referenced ascent was the first successful one-day climb of a route or peak, performed by the specified climber or party.
-
B.
secondAscentBy
Indicates that the related entity is the person, group, or expedition that made the second successful ascent of a particular route, peak, or climbing objective.
-
C.
firstOneDayAscentDate
Indicates the calendar date on which the first successful ascent of something was completed within a single day.
-
D.
notableAscent
Indicates that an entity is recognized for a significant rise, climb, or upward journey, such as an important ascent of a mountain or similar elevation.
-
E.
firstAscentBy
Indicates the person or party that first successfully ascended or climbed a particular route, peak, or feature.
- F. None of above. chosen
Provenance (4 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada579b07c8190a7b316f499911a2d |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:05 p.m.