Triple
T10855382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungurahua |
E256255
|
entity |
| Predicate | summitGlacierStatus |
P41455
|
FINISHED |
| Object | largely melted due to recent activity |
—
|
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: largely melted due to recent activity | Statement: [Tungurahua, summitGlacierStatus, largely melted due to recent activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitGlacierStatus Context triple: [Tungurahua, summitGlacierStatus, largely melted due to recent activity]
-
A.
glaciersStatus
chosen
Indicates the current condition or state of glaciers, such as their size, stability, or rate of change.
-
B.
summitStatus
Indicates the current state or outcome of a summit event, such as whether it is planned, ongoing, completed, or canceled.
-
C.
summitCrater
Indicates the relationship where a crater is located at or forms the summit of a volcanic or mountainous feature.
-
D.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
E.
hasGlacierAccess
Indicates that an entity has direct access to, or is reachable from, a glacier (e.g., via paths, routes, or physical adjacency).
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75135df24819090ce43afa3ea9b38 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.