Triple
T7046723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philemon Beecher Van Trump |
E163652
|
entity |
| Predicate | notableAscentDate |
P36469
|
FINISHED |
| Object | 1870-08-17 |
—
|
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: 1870-08-17 | Statement: [Philemon Beecher Van Trump, notableAscentDate, 1870-08-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAscentDate Context triple: [Philemon Beecher Van Trump, notableAscentDate, 1870-08-17]
-
A.
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.
-
B.
firstOneDayAscentDate
Indicates the calendar date on which the first successful ascent of something was completed within a single day.
-
C.
secondAscentDate
Indicates the date on which the second successful ascent or climb of something (such as a mountain or route) took place.
-
D.
firstFreeAscentDate
Indicates the date on which the first successful ascent of a route, peak, or climb was completed without the use of artificial aids for upward progress.
-
E.
climbDate
chosen
Indicates the date on which a particular climbing activity or ascent took place.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.