Triple
T3363112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olgovichi |
E70768
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Chernigov |
E149955
|
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: Chernigov | Statement: [Olgovichi, capital, Chernigov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chernigov Context triple: [Olgovichi, capital, Chernigov]
-
A.
Chernihiv
chosen
Chernihiv is a historic city in northern Ukraine known for its ancient churches, rich cultural heritage, and role as a regional administrative and memorial center.
-
B.
Rivne
Rivne is a city in western Ukraine that serves as an important regional administrative, economic, and cultural center.
-
C.
Orsha
Orsha is a historic city in eastern Belarus known as a regional transport hub and site of several significant battles.
-
D.
Pereiaslavl
Pereiaslavl was one of the principal urban centers of Kyivan Rus, serving as an important political, military, and cultural hub in medieval Eastern Europe.
-
E.
Smolensk
Smolensk is a historic city in western Russia near the Belarusian border, known for its strategic location and centuries-old fortifications.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26a5a508190948932769de0dbb3 |
completed | March 8, 2026, 5:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b37e503d94819082657f11d51aebca |
completed | March 13, 2026, 3:02 a.m. |
Created at: March 8, 2026, 3:13 p.m.