Triple
T19186987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nome Harbor |
E469725
|
entity |
| Predicate | navigationalSeason |
P93272
|
FINISHED |
| Object | primarily ice‑free in summer months |
—
|
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: primarily ice‑free in summer months | Statement: [Nome Harbor, navigationalSeason, primarily ice‑free in summer months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalSeason Context triple: [Nome Harbor, navigationalSeason, primarily ice‑free in summer months]
-
A.
navigationSeason
chosen
Indicates the time period or season during which navigation or travel along a route or waterway is possible or permitted.
-
B.
navigationSeasonInfluencedBy
Indicates that the conditions or characteristics of a navigation season are affected or determined by another factor or entity.
-
C.
ferrySeason
Indicates that a ferry service operates or is available during a specified season or time of year.
-
D.
recreationSeason
Indicates the time of year or specific season during which a recreational activity, facility, or area is typically used or available.
-
E.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f620f1f08190a0daaf0d1483d724 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.