Triple
T13284167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transpolar Drift Stream |
E316395
|
entity |
| Predicate | typicalSeaIceTransitTime |
P109310
|
FINISHED |
| Object | 2 to 4 years |
—
|
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: 2 to 4 years | Statement: [Transpolar Drift Stream, typicalSeaIceTransitTime, 2 to 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSeaIceTransitTime Context triple: [Transpolar Drift Stream, typicalSeaIceTransitTime, 2 to 4 years]
-
A.
seaIceType
Indicates the specific classification or category of sea ice associated with an entity (e.g., by age, thickness, or formation characteristics).
-
B.
typicalSeaIceCondition
Indicates the usual or characteristic state or properties of sea ice under normal environmental conditions.
-
C.
hasSeasonalSeaIce
Indicates that a body of water is covered by sea ice only during certain seasons or times of the year.
-
D.
hasSeaIce
Indicates that one entity possesses, contains, or is covered by sea ice in relation to another context or location.
-
E.
hasTypicalSeaIceType
Indicates the characteristic or commonly occurring type of sea ice associated with a given location or context.
- F. None of above. chosen
Provenance (4 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:27 p.m.