Triple
T2312941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iqaluit |
E50998
|
entity |
| Predicate | seaIcePresence |
P4995
|
FINISHED |
| Object | significant part of the year |
—
|
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: significant part of the year | Statement: [Iqaluit, seaIcePresence, significant part of the year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaIcePresence Context triple: [Iqaluit, seaIcePresence, significant part of the year]
-
A.
hasSeaIce
chosen
Indicates that one entity possesses, contains, or is covered by sea ice in relation to another context or location.
-
B.
seaIceType
Indicates the specific classification or category of sea ice associated with an entity (e.g., by age, thickness, or formation characteristics).
-
C.
hasSeaIceExtent
Indicates that a specified area or region possesses a measurable amount or coverage of sea ice over a given space or time.
-
D.
hasIcebergs
Indicates that one entity (typically a body of water or region) contains or is characterized by the presence of icebergs.
-
E.
seaIceMaximumExtent
Indicates the greatest spatial coverage or area that sea ice reaches during its annual or seasonal cycle.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.