Triple
T25778125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thwaites Glacier |
E649210
|
entity |
| Predicate | bedTopography |
P87992
|
FINISHED |
| Object | retrograde slope |
—
|
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: retrograde slope | Statement: [Thwaites Glacier, bedTopography, retrograde slope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bedTopography Context triple: [Thwaites Glacier, bedTopography, retrograde slope]
-
A.
floorTopography
Indicates the physical surface characteristics or contour of a floor, such as its texture, flatness, or unevenness.
-
B.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
-
C.
associatedTopography
chosen
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
D.
hasTopographicEffect
Indicates that one entity causes or contributes to a change or influence on the physical terrain or topography of another entity or area.
-
E.
topographicallyContrastedWith
Indicates that two geographic areas are compared or distinguished based on differences in their physical surface features or terrain.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe5e7d3481908a77848582404490 |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:35 a.m.