Triple
T6591651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amalia Glacier |
E159373
|
entity |
| Predicate | retreatType |
P71667
|
FINISHED |
| Object | rapid glacial retreat |
—
|
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: rapid glacial retreat | Statement: [Amalia Glacier, retreatType, rapid glacial retreat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retreatType Context triple: [Amalia Glacier, retreatType, rapid glacial retreat]
-
A.
placeOfRetreat
Indicates a relationship where a location serves as a refuge or retreat for an entity, typically used for rest, seclusion, or recovery.
-
B.
retreatCause
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
-
C.
resort
Indicates that one entity is used or turned to as a final or alternative option by another entity, often after other possibilities have been exhausted.
-
D.
typeOfReserve
Indicates that one entity is classified as a specific kind or category of reserve in relation to another entity.
-
E.
hasResortType
Indicates that an entity (such as a resort or accommodation) is associated with a specific category or type of resort (e.g., beach resort, ski resort, spa resort).
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c07bb434819096ec3e3b966042a5 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 1:55 p.m.