Triple

T15234524
Position Surface form Disambiguated ID Type / Status
Subject Principality of Chernigov E364089 entity
Predicate significantCity P12871 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: [Principality of Chernigov, significantCity, Bryansk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bryansk
Context triple: [Principality of Chernigov, significantCity, 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007d91e4881908ea52d11a3d4480a completed April 15, 2026, 9:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084a4c2cc81908c8acd3a1123208a completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 3:12 a.m.