Triple
T14387607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryansk Oblast |
E356765
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Bryansk |
E525726
|
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: Bryansk | Statement: [Bryansk Oblast, namedAfter, Bryansk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bryansk Context triple: [Bryansk Oblast, namedAfter, Bryansk]
-
A.
Bryansk
chosen
Bryansk is a historic industrial city in western Russia near the border with Ukraine and Belarus, known as a major transport hub and regional administrative center.
-
B.
Ryazhsk
Ryazhsk is a historic town in Ryazan Oblast, Russia, known as a former local administrative center dating back to the Russian Empire.
-
C.
Ryazan
Ryazan is a historic city in western Russia known for its medieval kremlin, role as a regional cultural and economic center, and legacy as one of the country’s oldest urban settlements.
-
D.
Oryol
Oryol was a notable warship of the Imperial Russian Navy, recognized for its role in Russia’s early modern naval history.
-
E.
Belgorod
Belgorod is a city in western Russia near the Ukrainian border, historically significant as a strategic site of major World War II battles and offensives.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90283b9c8190b50d30ad58bfe085 |
completed | April 14, 2026, 7:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0025e6bc748190b8099e7559569a90 |
completed | May 10, 2026, 6:29 a.m. |
Created at: April 10, 2026, 1:16 a.m.