Triple
T19879377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bay (Livingston Island) |
E477726
|
entity |
| Predicate | typicalSeaIce |
P95933
|
FINISHED |
| Object | seasonal sea ice cover |
—
|
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: seasonal sea ice cover | Statement: [South Bay (Livingston Island), typicalSeaIce, seasonal sea ice cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSeaIce Context triple: [South Bay (Livingston Island), typicalSeaIce, seasonal sea ice cover]
-
A.
typicalSeaIceCondition
Indicates the usual or characteristic state or properties of sea ice under normal environmental conditions.
-
B.
seaIceType
Indicates the specific classification or category of sea ice associated with an entity (e.g., by age, thickness, or formation characteristics).
-
C.
hasTypicalSeaIceType
Indicates the characteristic or commonly occurring type of sea ice associated with a given location or context.
-
D.
typicalSeaIceTransitTime
Indicates the usual amount of time it takes to travel through or across sea ice under normal conditions.
-
E.
hasSeasonalSeaIce
chosen
Indicates that a body of water is covered by sea ice only during certain seasons or times of the year.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658dd869c81908aed91ee767f5f3d |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.