Triple
T15054158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talum Glacier |
E379444
|
entity |
| Predicate | hasPrimaryAblationProcess |
P117144
|
FINISHED |
| Object | melting |
—
|
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: melting | Statement: [Talum Glacier, hasPrimaryAblationProcess, melting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAblationProcess Context triple: [Talum Glacier, hasPrimaryAblationProcess, melting]
-
A.
primaryAblation
Indicates that an entity is the main or original target of an ablation (removal, destruction, or disabling) process.
-
B.
hasSurgery
Indicates that a surgical procedure is performed on or undergone by an entity.
-
C.
hadProcedure
Indicates that a subject underwent or received a specific medical or clinical procedure.
-
D.
hasSpecialProcedure
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
E.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda92091c81909180f486edf01405 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:01 a.m.