Triple

T28413331
Position Surface form Disambiguated ID Type / Status
Subject Gakona, Alaska E719727 entity
Predicate locatedOn P40 FINISHED
Object Gakona River
The Gakona River is a glacially fed river in south-central Alaska that flows through the Copper River Basin and supports local ecosystems and small communities such as Gakona.
E2294771 NE 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: Gakona River | Statement: [Gakona, Alaska, locatedOn, Gakona River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Gakona River
Triple: [Gakona, Alaska, locatedOn, Gakona River]
Generated description
The Gakona River is a glacially fed river in south-central Alaska that flows through the Copper River Basin and supports local ecosystems and small communities such as Gakona.

Provenance (5 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_69eff6f0f37c8190b37bc6fab08a9449 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64dbe401081909ea87d252a09101d completed May 2, 2026, 7:17 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7c1be6dc4c81909d43189c04f0bd78 completed Aug. 12, 2026, 7:08 a.m.
NEDg Description generation batch_6a7c1c569b0081908e80af4ef169e109 completed Aug. 12, 2026, 7:10 a.m.
NED2 Entity disambiguation (via description) batch_6a7c1cbacdcc8190a8fce3d95a4311a4 completed Aug. 12, 2026, 7:11 a.m.
Created at: April 28, 2026, 1:28 a.m.