Triple
T2247707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horace Bénédict de Saussure |
E49544
|
entity |
| Predicate | climbDate |
P36469
|
FINISHED |
| Object | 1787-08-03 |
—
|
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: 1787-08-03 | Statement: [Horace Bénédict de Saussure, climbDate, 1787-08-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbDate Context triple: [Horace Bénédict de Saussure, climbDate, 1787-08-03]
-
A.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
B.
firstWinterAscentDate
Indicates the calendar date on which the first successful winter ascent of something (typically a route, peak, or climb) was completed.
-
C.
climbingStatus
Indicates the current state or condition of an entity with respect to a climbing activity or process (e.g., whether it is climbing, has climbed, or is not climbing).
-
D.
firstAscentYear
Indicates the calendar year in which something (typically a route, peak, or climb) was first successfully ascended.
-
E.
climbingBanEffectiveFrom
Indicates the date or point in time from which a climbing ban starts to apply.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0ed5c38819080b45ea398fb59f2 |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.