Triple
T1346046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amundsen Sea |
E28572
|
entity |
| Predicate | seaLevelRiseContribution |
P8157
|
FINISHED |
| Object | disproportionately large relative to its area |
—
|
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: disproportionately large relative to its area | Statement: [Amundsen Sea, seaLevelRiseContribution, disproportionately large relative to its area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaLevelRiseContribution Context triple: [Amundsen Sea, seaLevelRiseContribution, disproportionately large relative to its area]
-
A.
seaLevelCharacteristic
Indicates a characteristic, property, or attribute specifically related to sea level.
-
B.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
C.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
D.
waterMassInfluence
chosen
Indicates how the presence, amount, or distribution of water mass affects or modifies another entity or system.
-
E.
partlyBelowSeaLevel
Indicates that an entity’s elevation is such that some, but not all, of it lies below 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23e84188190b0395c57dd45b62a |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.