Triple
T7581852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Hemisphere ice sheets |
E179505
|
entity |
| Predicate | meltwaterDischargeTriggered |
P50125
|
FINISHED |
| Object | abrupt climate events |
—
|
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: abrupt climate events | Statement: [Northern Hemisphere ice sheets, meltwaterDischargeTriggered, abrupt climate events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meltwaterDischargeTriggered Context triple: [Northern Hemisphere ice sheets, meltwaterDischargeTriggered, abrupt climate events]
-
A.
hasMeltwaterContributionTo
chosen
Indicates that one entity contributes meltwater (from melting ice or snow) to another entity, such as a water body or hydrological system.
-
B.
glacierFlowRate
Indicates the rate at which a glacier moves or flows over a given distance in a specified time.
-
C.
floodEvent
Indicates an occurrence of a flooding event affecting a location, time period, or set of impacted entities.
-
D.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
E.
floodSeasonCause
Indicates the cause or contributing factor responsible for a particular flood season occurring.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f978341081909e009c410ffc5039 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.