Triple
T17760580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadym River |
E443358
|
entity |
| Predicate | hasTownOnBank |
P847
|
FINISHED |
| Object | Nadym |
—
|
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: Nadym | Statement: [Nadym River, hasTownOnBank, Nadym]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nadym Context triple: [Nadym River, hasTownOnBank, Nadym]
-
A.
Nadym
chosen
Nadym is a town in the Yamalo-Nenets Autonomous Okrug of Russia, known as a regional center for the natural gas industry and served by its own airport.
-
B.
Aldan
Aldan is a mining town in Russia’s Sakha Republic known for its significant gold deposits and remote Siberian location.
-
C.
Khopyor
Khopyor is a major river in southwestern Russia that flows through the Central Russian Upland before joining the Don River.
-
D.
Daur
The Daur are a Mongolic ethnic group of northeastern China, traditionally living along the Heilongjiang (Amur) River and known for their distinct language, culture, and history as borderland farmers and hunters.
-
E.
Daur
Daur is a town in Pakistan’s Sindh province, known as a local commercial and agricultural center within the Nawabshah (Shaheed Benazirabad) District.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48421c3048190b26864b72aad0d70 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 10:11 a.m.