Triple
T19061048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldan River |
E466531
|
entity |
| Predicate | hasCityOnBank |
P7935
|
FINISHED |
| Object | Aldan |
—
|
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: Aldan | Statement: [Aldan River, hasCityOnBank, Aldan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aldan Context triple: [Aldan River, hasCityOnBank, Aldan]
-
A.
Aldan
chosen
Aldan is a mining town in Russia’s Sakha Republic known for its significant gold deposits and remote Siberian location.
-
B.
Nadym
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.
-
C.
Tanasi
Tanasi was a historic Overhill Cherokee town in present-day Tennessee that gave the state its name and served as an early political center for the Cherokee.
-
D.
Nednai
Nednai is an alternate name for the Nednhi Apache, a subgroup of the Chiricahua Apache people historically living in northern Mexico and the U.S. Southwest.
-
E.
Naedo
Naedo is a small island that forms part of the coastal city of Geoje in South Gyeongsang Province, South Korea.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e194c854819085a0a48d22c5cebd |
completed | April 20, 2026, 8:19 a.m. |
Created at: April 10, 2026, 12:03 p.m.