Triple
T18863836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darby Field |
E461380
|
entity |
| Predicate | ascentDate |
P133227
|
FINISHED |
| Object | 1642 |
—
|
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: 1642 | Statement: [Darby Field, ascentDate, 1642]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascentDate Context triple: [Darby Field, ascentDate, 1642]
-
A.
ascentStageImpactDate
Indicates the calendar date on which an ascent stage impacts a surface or target body.
-
B.
secondAscentDate
Indicates the date on which the second successful ascent or climb of something (such as a mountain or route) took place.
-
C.
approximateAscentTime
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
-
D.
firstOneDayAscentDate
Indicates the calendar date on which the first successful ascent of something was completed within a single day.
-
E.
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.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a304d4819092f14b7932d01afe |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.