Triple
T11722395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose |
E278669
|
entity |
| Predicate | firstAscentDurationDays |
P100989
|
FINISHED |
| Object | 47 |
—
|
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: 47 | Statement: [The Nose, firstAscentDurationDays, 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentDurationDays Context triple: [The Nose, firstAscentDurationDays, 47]
-
A.
firstFreeAscentDuration
Indicates the length of time taken to complete the first free ascent of a route or climb.
-
B.
firstOneDayAscentDate
Indicates the calendar date on which the first successful ascent of something was completed within a single day.
-
C.
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.
-
D.
firstAscentStatus
Indicates whether and how a first ascent of something (such as a route, peak, or feature) has been achieved or recorded.
-
E.
firstAscentYear
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:40 p.m.