Triple
T12086670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rzhevsky Uyezd |
E287822
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Rzhev |
E280196
|
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: Rzhev | Statement: [Rzhevsky Uyezd, namedAfter, Rzhev]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rzhev Context triple: [Rzhevsky Uyezd, namedAfter, Rzhev]
-
A.
Rzhev
chosen
Rzhev is a historic town in western Russia known for its strategic location on the Volga River and as the site of major World War II battles.
-
B.
Pokrovsk
Pokrovsk is the former name of the Russian city now known as Engels, located in Saratov Oblast on the Volga River.
-
C.
Pokrovsk
Pokrovsk is a city in eastern Ukraine that serves as an important industrial and transport hub within Donetsk Oblast.
-
D.
Vyazma
Vyazma is a historic town in Smolensk Oblast, western Russia, known for its strategic military significance, particularly during World War II.
-
E.
Kozelsk
Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91514c78c8190bc1cd569e524e8b4 |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e42cd588190835b3e8160bdbba5 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:48 p.m.