Triple
T20328987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neryungrinsky District |
E492416
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object |
Serebryany Bor
Serebryany Bor is a rural settlement located within the Neryungrinsky District of the Sakha Republic in Russia.
|
E1424871
|
NE FINISHED |
How this triple was built (4 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: Serebryany Bor | Statement: [Neryungrinsky District, hasSettlement, Serebryany Bor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Serebryany Bor Context triple: [Neryungrinsky District, hasSettlement, Serebryany Bor]
-
A.
Khreshchatyi Yar
Khreshchatyi Yar is the historic ravine area in central Kyiv whose name gave rise to the city’s main thoroughfare, Khreshchatyk Street.
-
B.
Medveditsa
Medveditsa is a river in southwestern Russia that flows through the Volgograd and Saratov regions before joining the Don River.
-
C.
Vykhino
Vykhino is a Moscow Metro station serving the Tagansko–Krasnopresnenskaya Line in the southeastern part of the city.
-
D.
Polevskoy
Polevskoy is an industrial town in Russia’s Ural region, historically associated with copper mining and metallurgy.
-
E.
Yamskaya
Yamskaya is a name element associated with several historic streets and districts in Moscow, traditionally linked to coachmen’s settlements along major travel routes.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Serebryany Bor Triple: [Neryungrinsky District, hasSettlement, Serebryany Bor]
Generated description
Serebryany Bor is a rural settlement located within the Neryungrinsky District of the Sakha Republic in Russia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Serebryany Bor Target entity description: Serebryany Bor is a rural settlement located within the Neryungrinsky District of the Sakha Republic in Russia.
-
A.
Khreshchatyi Yar
Khreshchatyi Yar is the historic ravine area in central Kyiv whose name gave rise to the city’s main thoroughfare, Khreshchatyk Street.
-
B.
Medveditsa
Medveditsa is a river in southwestern Russia that flows through the Volgograd and Saratov regions before joining the Don River.
-
C.
Vykhino
Vykhino is a Moscow Metro station serving the Tagansko–Krasnopresnenskaya Line in the southeastern part of the city.
-
D.
Polevskoy
Polevskoy is an industrial town in Russia’s Ural region, historically associated with copper mining and metallurgy.
-
E.
Yamskaya
Yamskaya is a name element associated with several historic streets and districts in Moscow, traditionally linked to coachmen’s settlements along major travel routes.
- F. None of above. chosen
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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e637e48190b5582e97fe1000c0 |
completed | April 20, 2026, 7 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08694f802c8190b1f06c0a1c71cde4 |
completed | May 16, 2026, 12:55 p.m. |
| NEDg | Description generation | batch_6a0869f7b4208190858fdeae882e008d |
completed | May 16, 2026, 12:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a086a893f1c81909bc40e3c4db0e147 |
completed | May 16, 2026, 1 p.m. |
Created at: April 16, 2026, 11:22 a.m.