Triple
T12845436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabesna Glacier |
E307162
|
entity |
| Predicate | feedsRiver |
P40305
|
FINISHED |
| Object | Nabesna River |
—
|
NE NERFINISHED |
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: Nabesna River | Statement: [Nabesna Glacier, feedsRiver, Nabesna River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nabesna River Context triple: [Nabesna Glacier, feedsRiver, Nabesna River]
-
A.
Nabesna River
chosen
The Nabesna River is a remote glacial river in eastern Alaska that drains the Nabesna Glacier and flows through Wrangell–St. Elias National Park and Preserve.
-
B.
Nesu River
The Nesu River is a lesser-known river in central India that feeds into the Tapti River as part of its drainage system.
-
C.
Neya River
The Neya River is a waterway in western Russia that flows through Kostroma Oblast and serves as a tributary within the Volga river basin.
-
D.
Nerekhta River
The Nerekhta River is a small waterway in central Russia that flows through the town of Nerekhta and forms part of the region’s local river system.
-
E.
Lososinka River
The Lososinka River is a small river in the Republic of Karelia, Russia, that flows through the city of Petrozavodsk into Lake Onega.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff3a7208190b93f6292ed5efc07 |
completed | April 10, 2026, 9:47 p.m. |
Created at: April 9, 2026, 5:36 p.m.