Triple
T6639676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prydz Bay region |
E150552
|
entity |
| Predicate | hasSeaIceRegime |
P22448
|
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: [Prydz Bay region, hasSeaIceRegime, seasonal sea ice cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaIceRegime Context triple: [Prydz Bay region, hasSeaIceRegime, seasonal sea ice cover]
-
A.
hasSeaIce
Indicates that one entity possesses, contains, or is covered by sea ice in relation to another context or location.
-
B.
hasSeaIceExtent
Indicates that a specified area or region possesses a measurable amount or coverage of sea ice over a given space or time.
-
C.
hasTypicalIceRegime
chosen
Indicates that there is a characteristic or commonly occurring pattern of ice conditions associated with the referenced entity.
-
D.
hasTypicalSeaIceType
Indicates the characteristic or commonly occurring type of sea ice associated with a given location or context.
-
E.
hasSurroundingSeaIceSeason
Indicates the period during which a given location is surrounded by sea ice.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 2 p.m.