Triple
T37285466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinizas |
E925520
|
entity |
| Predicate | firstAscentIllinizaNorteYear |
P8812
|
FINISHED |
| Object | 1912 |
—
|
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: 1912 | Statement: [Illinizas, firstAscentIllinizaNorteYear, 1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentIllinizaNorteYear Context triple: [Illinizas, firstAscentIllinizaNorteYear, 1912]
-
A.
firstAscentYear
chosen
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
B.
firstWinterAscentYear
Indicates the year in which the first successful winter ascent of something (such as a mountain or route) was completed.
-
C.
firstFreeAscentYear
Indicates the year in which the first successful free ascent of a route or peak was completed.
-
D.
firstWinterAscentDate
Indicates the calendar date on which the first successful winter ascent of something (typically a route, peak, or climb) was completed.
-
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.
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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.