Triple
T9582306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Прямухино |
E231202
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | Прямухино |
E231202
|
NE FINISHED |
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: Прямухино | Statement: [Прямухино, nativeName, Прямухино]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Прямухино Context triple: [Прямухино, nativeName, Прямухино]
-
A.
Прямухино
chosen
Прямухино — это небольшое российское сельское поселение, известное как родовое имение семьи Бакуниных и связанное с жизнью анархиста Михаила Бакунина.
-
B.
Devyatkino
Devyatkino is a metro station serving as the northern terminus of the Red Line (Line 1) of the Saint Petersburg Metro in Russia.
-
C.
Ramenskoye
Ramenskoye is a town in Moscow Oblast, Russia, located southeast of Moscow and known for its industrial base and proximity to major Moscow airports.
-
D.
Romashkovo
Romashkovo is a rural locality in Moscow Oblast, Russia, known as a suburban settlement within the Odintsovsky District near Moscow.
-
E.
Noginsk
Noginsk is a town in western Russia that serves as an industrial and transport center east of Moscow.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cd59008190888eb11f00f61994 |
completed | April 1, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc389c248190ac10adfc49a1240d |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:05 p.m.