Triple
T14814503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arzamas |
E348274
|
entity |
| Predicate | administrativeCenterOf |
P383
|
FINISHED |
| Object |
Arzamassky District (de facto, not part of district)
Arzamassky District (de facto, not part of district) is an administrative district in Nizhny Novgorod Oblast, Russia, whose functions are effectively centered in the nearby city of Arzamas despite that city being administratively separate from the district itself.
|
E1120497
|
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: Arzamassky District (de facto, not part of district) | Statement: [Arzamas, administrativeCenterOf, Arzamassky District (de facto, not part of district)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arzamassky District (de facto, not part of district) Context triple: [Arzamas, administrativeCenterOf, Arzamassky District (de facto, not part of district)]
-
A.
Azovsky District (de facto, though not part of it)
Azovsky District (de facto, though not part of it) is an administrative district in Russia’s Rostov Oblast that is functionally centered on the city of Azov, despite the city being administratively separate from the district itself.
-
B.
Chitinsky District (de facto)
Chitinsky District (de facto) is an administrative district in Zabaykalsky Krai, Russia, for which the city of Chita serves as the administrative center.
-
C.
Vologodsky District (de facto, while not part of it)
Vologodsky District (de facto, while not part of it) is a municipal district in Vologda Oblast, Russia, whose administrative functions are centered in the city of Vologda even though the city itself is administratively separate from the district.
-
D.
Rybinsky District (de facto, though not part of it)
Rybinsky District (de facto, though not part of it) is an administrative district in Yaroslavl Oblast, Russia, whose functions are effectively centered in the nearby city of Rybinsk despite the city not being formally included within the district’s territory.
-
E.
Maykopsky District (de facto, without being part of it)
Maykopsky District (de facto, without being part of it) is a municipal district in the Republic of Adygea, Russia, whose administrative functions are carried out from the nearby city of Maykop, even though the city is not formally included within the district’s territory.
- 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: Arzamassky District (de facto, not part of district) Triple: [Arzamas, administrativeCenterOf, Arzamassky District (de facto, not part of district)]
Generated description
Arzamassky District (de facto, not part of district) is an administrative district in Nizhny Novgorod Oblast, Russia, whose functions are effectively centered in the nearby city of Arzamas despite that city being administratively separate from the district itself.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Arzamassky District (de facto, not part of district) Target entity description: Arzamassky District (de facto, not part of district) is an administrative district in Nizhny Novgorod Oblast, Russia, whose functions are effectively centered in the nearby city of Arzamas despite that city being administratively separate from the district itself.
-
A.
Azovsky District (de facto, though not part of it)
Azovsky District (de facto, though not part of it) is an administrative district in Russia’s Rostov Oblast that is functionally centered on the city of Azov, despite the city being administratively separate from the district itself.
-
B.
Chitinsky District (de facto)
Chitinsky District (de facto) is an administrative district in Zabaykalsky Krai, Russia, for which the city of Chita serves as the administrative center.
-
C.
Vologodsky District (de facto, while not part of it)
Vologodsky District (de facto, while not part of it) is a municipal district in Vologda Oblast, Russia, whose administrative functions are centered in the city of Vologda even though the city itself is administratively separate from the district.
-
D.
Rybinsky District (de facto, though not part of it)
Rybinsky District (de facto, though not part of it) is an administrative district in Yaroslavl Oblast, Russia, whose functions are effectively centered in the nearby city of Rybinsk despite the city not being formally included within the district’s territory.
-
E.
Maykopsky District (de facto, without being part of it)
Maykopsky District (de facto, without being part of it) is a municipal district in the Republic of Adygea, Russia, whose administrative functions are carried out from the nearby city of Maykop, even though the city is not formally included within the district’s territory.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe0e89c81908c0e1fe2bc3ebcfc |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24cca0b88190b20a6c7dd77b8146 |
completed | May 8, 2026, 6 p.m. |
| NEDg | Description generation | batch_69fe291c69fc8190b29d6d2ca89ce6ec |
completed | May 8, 2026, 6:19 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe29a093d0819092ae65dc66a3c190 |
completed | May 8, 2026, 6:21 p.m. |
Created at: April 10, 2026, 1:48 a.m.