Triple
T7681047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naknek, Alaska |
E173992
|
entity |
| Predicate | primaryIndustrySeason |
P78901
|
FINISHED |
| Object | summer salmon season |
—
|
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: summer salmon season | Statement: [Naknek, Alaska, primaryIndustrySeason, summer salmon season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryIndustrySeason Context triple: [Naknek, Alaska, primaryIndustrySeason, summer salmon season]
-
A.
growingSeason
Indicates the period of the year during which growth or development actively occurs for the referenced entity.
-
B.
affectedSeason
Indicates that one entity has an influence on, or causes a change in, a particular season.
-
C.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
D.
primarySectorCoverage
Indicates that one entity serves as the main or dominant sector in which another entity operates, focuses, or provides coverage.
-
E.
basedOnSeason
Indicates that something is determined, influenced, or derived according to a particular season or time of year.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7048a01508190bc2e9ae8b863486c |
completed | March 27, 2026, 10:28 p.m. |
Created at: March 27, 2026, 4:01 p.m.