Triple
T17274192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Komsomolskoye |
E419342
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object |
Komsomolskoye
Komsomolskoye is a village in Chechnya, Russia, known as the site of a major battle during the Second Chechen War.
|
E1314214
|
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: Komsomolskoye | Statement: [Battle of Komsomolskoye, location, Komsomolskoye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Komsomolskoye Context triple: [Battle of Komsomolskoye, location, Komsomolskoye]
-
A.
Komsomolskaya
Komsomolskaya is one of Moscow Metro’s most famous and ornate stations, renowned for its grand Baroque-style decor and elaborate mosaics.
-
B.
Petrovskoye
Petrovskoye was the original Russian fortress settlement that later developed into the modern city of Makhachkala in Dagestan, Russia.
-
C.
Kireyevsk
Kireyevsk is a small industrial town in western Russia known for its coal-mining history and location within the Tula region.
-
D.
Sestroretsk
Sestroretsk is a town in northwestern Russia, now part of Saint Petersburg, historically known for its arms factory and seaside resort area on the Gulf of Finland.
-
E.
Nikolskoye
Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
- 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: Komsomolskoye Triple: [Battle of Komsomolskoye, location, Komsomolskoye]
Generated description
Komsomolskoye is a village in Chechnya, Russia, known as the site of a major battle during the Second Chechen War.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Komsomolskoye Target entity description: Komsomolskoye is a village in Chechnya, Russia, known as the site of a major battle during the Second Chechen War.
-
A.
Komsomolskaya
Komsomolskaya is one of Moscow Metro’s most famous and ornate stations, renowned for its grand Baroque-style decor and elaborate mosaics.
-
B.
Petrovskoye
Petrovskoye was the original Russian fortress settlement that later developed into the modern city of Makhachkala in Dagestan, Russia.
-
C.
Kireyevsk
Kireyevsk is a small industrial town in western Russia known for its coal-mining history and location within the Tula region.
-
D.
Sestroretsk
Sestroretsk is a town in northwestern Russia, now part of Saint Petersburg, historically known for its arms factory and seaside resort area on the Gulf of Finland.
-
E.
Nikolskoye
Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4c209c81909c713ed78f2cb19a |
completed | April 19, 2026, 1:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a03ac5273648190b3a1e01ea9ccde9a |
completed | May 12, 2026, 10:40 p.m. |
| NEDg | Description generation | batch_6a03ad4d5bcc8190a5e065a5bb897400 |
completed | May 12, 2026, 10:44 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a03af1fb1e0819095c9e8cb5528ce30 |
completed | May 12, 2026, 10:52 p.m. |
Created at: April 10, 2026, 5:40 a.m.