Triple
T7283185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocciamelone |
E163799
|
entity |
| Predicate | firstAscentType |
P27613
|
FINISHED |
| Object | religious vow ascent |
—
|
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: religious vow ascent | Statement: [Rocciamelone, firstAscentType, religious vow ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAscentType Context triple: [Rocciamelone, firstAscentType, religious vow ascent]
-
A.
firstAscent
Indicates that an entity represents the earliest known successful ascent or climb of a particular route, peak, or feature.
-
B.
firstAscentStatus
Indicates whether and how a first ascent of something (such as a route, peak, or feature) has been achieved or recorded.
-
C.
firstAscentStyle
chosen
Indicates the style or manner in which the first successful ascent of a route or peak was carried out.
-
D.
firstAscentFrom
Indicates the starting location or route from which the first successful ascent of something (typically a peak or climb) was made.
-
E.
firstAscentRouteOf
Indicates that a particular climbing route is the one used for the first successful ascent of a specific peak or climbing objective.
- 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_69c6886093b88190a254b1ce6db8bae7 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb4ec2088190a6713eaa221d49a6 |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.