Triple
T3687256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorner Glacier |
E78253
|
entity |
| Predicate | hasRetreatCause |
P23193
|
FINISHED |
| Object | climate change |
—
|
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: climate change | Statement: [Gorner Glacier, hasRetreatCause, climate change]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetreatCause Context triple: [Gorner Glacier, hasRetreatCause, climate change]
-
A.
retreatCause
chosen
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
-
B.
hasRetreatedSince
Indicates that an entity has withdrawn or moved back from a position or engagement at some point after a specified reference time or event.
-
C.
isRetreating
Indicates that an entity is moving away from a location, opponent, or situation, typically to withdraw or escape from engagement.
-
D.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
E.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c7e2bc81909356c8b0ed90feed |
completed | March 8, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.