Triple
T6201704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Karisimbi |
E138647
|
entity |
| Predicate | hasTypicalAscentDuration |
P40570
|
FINISHED |
| Object | 2 days |
—
|
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: 2 days | Statement: [Mount Karisimbi, hasTypicalAscentDuration, 2 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAscentDuration Context triple: [Mount Karisimbi, hasTypicalAscentDuration, 2 days]
-
A.
durationTypicalAscent
chosen
Indicates the typical amount of time required to complete an ascent.
-
B.
firstFreeAscentDuration
Indicates the length of time taken to complete the first free ascent of a route or climb.
-
C.
hasFirstRecordedAscent
Indicates that a particular ascent is the earliest known or documented successful climb of a specific route, peak, or climbing objective.
-
D.
typicalAscentStyle
Indicates the usual or characteristic manner or technique by which an ascent or climb is performed.
-
E.
typicalAscentStartPoint
Indicates the usual or most common location from which an ascent or climb is begun.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062559bcc81908942bb4d25fe8158 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.