Triple
T26185899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Antarctic Ice Sheet |
E654826
|
entity |
| Predicate | potentialSeaLevelRiseIfMelted |
P8806
|
FINISHED |
| Object | about 50–53 meters |
—
|
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: about 50–53 meters | Statement: [East Antarctic Ice Sheet, potentialSeaLevelRiseIfMelted, about 50–53 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialSeaLevelRiseIfMelted Context triple: [East Antarctic Ice Sheet, potentialSeaLevelRiseIfMelted, about 50–53 meters]
-
A.
hasMeltwaterContributionTo
Indicates that one entity contributes meltwater (from melting ice or snow) to another entity, such as a water body or hydrological system.
-
B.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
C.
emergedAboveSeaLevel
Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
-
D.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
E.
seaLevelCharacteristic
chosen
Indicates a characteristic, property, or attribute specifically related to sea level.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c9df1ac8190a31d3a3fea0b2e16 |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:42 p.m.