Triple
T23033604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldansky District |
E573533
|
entity |
| Predicate | administrativeCenter |
P1474
|
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: [Aldansky District, administrativeCenter, Aldan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aldan Context triple: [Aldansky District, administrativeCenter, 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.
Youra
Youra is a given name most notably borne by Youra Livchitz, a Belgian resistance fighter during World War II.
-
E.
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.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18482e78c8190a89681eec2edb812 |
completed | April 29, 2026, 4:09 a.m. |
Created at: April 17, 2026, 3:53 p.m.