Triple
T11081901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Napaskiak, Alaska |
E262014
|
entity |
| Predicate | summerAccess |
P97114
|
FINISHED |
| Object | boat on the Kuskokwim River |
—
|
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: boat on the Kuskokwim River | Statement: [Napaskiak, Alaska, summerAccess, boat on the Kuskokwim River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerAccess Context triple: [Napaskiak, Alaska, summerAccess, boat on the Kuskokwim River]
-
A.
summerHomeOf
Indicates that a location serves as a seasonal or vacation residence for a person or group, specifically used during the summer.
-
B.
summerBase
Indicates a base or location where an entity is situated or operates specifically during the summer season.
-
C.
summerRole
Indicates a role, position, or function that an entity holds specifically during the summer period.
-
D.
summerPhase
Indicates the specific stage or period within the summer season that an entity is in or associated with.
-
E.
summerFeature
Indicates that something is a characteristic, attraction, or condition specifically associated with or prominent during the summer season.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799985650819089b2c0f35a212414 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.