Triple
T17735349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis Glacier |
E442698
|
entity |
| Predicate | hasRetreatedSignificantlySince |
P25139
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Lewis Glacier, hasRetreatedSignificantlySince, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetreatedSignificantlySince Context triple: [Lewis Glacier, hasRetreatedSignificantlySince, mid-20th century]
-
A.
hasRetreatedSince
chosen
Indicates that an entity has withdrawn or moved back from a position or engagement at some point after a specified reference time or event.
-
B.
hasRetreated
Indicates that an entity has withdrawn or moved back from a previous position, engagement, or situation.
-
C.
retreatedDuring
Indicates that an entity withdrew or pulled back during the time span or event specified by another entity.
-
D.
retreatedThrough
Indicates that an entity moved back or withdrew by passing through a specified location, route, or medium.
-
E.
isRetreating
Indicates that an entity is moving away from a location, opponent, or situation, typically to withdraw or escape from engagement.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478eaff6c81909c7bd438b8c6c987 |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.