Triple
T1101361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Semeru |
E24386
|
entity |
| Predicate | typicalSummitActivity |
P24146
|
FINISHED |
| Object | frequent small explosions |
—
|
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: frequent small explosions | Statement: [Mount Semeru, typicalSummitActivity, frequent small explosions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSummitActivity Context triple: [Mount Semeru, typicalSummitActivity, frequent small explosions]
-
A.
reachesSummit
Indicates that an entity successfully arrives at or attains the highest point or summit of something.
-
B.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
-
C.
climbingSeason
Indicates the period during which climbing an object, route, or area is typically allowed, feasible, or considered optimal.
-
D.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
-
E.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9c079f48190a0e0ddda182f7a01 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:43 p.m.