Triple
T7268257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Glacier |
E161033
|
entity |
| Predicate | retreatBegan |
P76043
|
FINISHED |
| Object | early 1980s |
—
|
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: early 1980s | Statement: [Columbia Glacier, retreatBegan, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retreatBegan Context triple: [Columbia Glacier, retreatBegan, early 1980s]
-
A.
retreatCause
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
-
B.
isRetreating
Indicates that an entity is moving away from a location, opponent, or situation, typically to withdraw or escape from engagement.
-
C.
hasRetreated
Indicates that an entity has withdrawn or moved back from a previous position, engagement, or situation.
-
D.
placeOfRetreat
Indicates a relationship where a location serves as a refuge or retreat for an entity, typically used for rest, seclusion, or recovery.
-
E.
retreatType
Indicates the specific kind or category of retreat associated with an event, action, or 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb088dac8190b353f6ea3d686025 |
completed | March 27, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69c6e76876608190ac4652bc7153302e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb06acd881908a1735fbbbd5756f |
completed | March 27, 2026, 8:39 p.m. |
Created at: March 27, 2026, 2:58 p.m.