Triple
T10667759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyman Glacier |
E251399
|
entity |
| Predicate | hasChange |
P9313
|
FINISHED |
| Object | area loss over recent decades |
—
|
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: area loss over recent decades | Statement: [Lyman Glacier, hasChange, area loss over recent decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChange Context triple: [Lyman Glacier, hasChange, area loss over recent decades]
-
A.
hasResultingChange
Indicates that one entity causes or leads to a specific change or transformation in another entity or state.
-
B.
hasDesignChange
Indicates that an entity has undergone a modification or alteration to its original design.
-
C.
hasDelta
chosen
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
-
D.
hasChangeControl
Indicates that an entity is subject to a defined process for reviewing, approving, and managing modifications or updates.
-
E.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f860790c81909c2c1d3c489ec5b4 |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.