Triple
T13129747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyborgsky District |
E311936
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object |
Sampsonievsky
Sampsonievsky is a municipal settlement located within the Vyborgsky District of Saint Petersburg, Russia.
|
E1041841
|
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: Sampsonievsky | Statement: [Vyborgsky District, containsSettlement, Sampsonievsky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sampsonievsky Context triple: [Vyborgsky District, containsSettlement, Sampsonievsky]
-
A.
Vyazemsky
Vyazemsky is a small town in Russia’s Far Eastern Federal District, serving as an administrative center within Khabarovsk Krai.
-
B.
Paveletskaya
Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s network.
-
C.
Artyomovsky
Artyomovsky is a town in Russia’s Ural region known for its industrial base and role as a local administrative center.
-
D.
Kamenskiy
Kamenskiy is a Slavic surname, commonly transliterated from Russian or related languages, borne by various individuals across Eastern Europe and the former Soviet Union.
-
E.
Skobelevskaya
Skobelevskaya is a Moscow Metro station serving the Severnoye Butovo District in the south of Moscow.
- 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: Sampsonievsky Triple: [Vyborgsky District, containsSettlement, Sampsonievsky]
Generated description
Sampsonievsky is a municipal settlement located within the Vyborgsky District of Saint Petersburg, Russia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Sampsonievsky Target entity description: Sampsonievsky is a municipal settlement located within the Vyborgsky District of Saint Petersburg, Russia.
-
A.
Vyazemsky
Vyazemsky is a small town in Russia’s Far Eastern Federal District, serving as an administrative center within Khabarovsk Krai.
-
B.
Paveletskaya
Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s network.
-
C.
Artyomovsky
Artyomovsky is a town in Russia’s Ural region known for its industrial base and role as a local administrative center.
-
D.
Kamenskiy
Kamenskiy is a Slavic surname, commonly transliterated from Russian or related languages, borne by various individuals across Eastern Europe and the former Soviet Union.
-
E.
Skobelevskaya
Skobelevskaya is a Moscow Metro station serving the Severnoye Butovo District in the south of Moscow.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819bfd348190a22d44f837877e1c |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7460c05bc819089cdd004bb07c492 |
completed | May 3, 2026, 12:56 p.m. |
| NEDg | Description generation | batch_69f749ffd5d4819096cee1b27838d7d3 |
completed | May 3, 2026, 1:13 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f74a58aa948190978568028cc5a445 |
completed | May 3, 2026, 1:15 p.m. |
Created at: April 9, 2026, 9:07 p.m.