Triple
T6632343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernihiv |
E149955
|
entity |
| Predicate | alternativeName |
P39
|
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: [Chernihiv, alternativeName, Chernigov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chernigov Context triple: [Chernihiv, alternativeName, Chernigov]
-
A.
Berehove
Berehove is a town in western Ukraine’s Zakarpattia region known for its significant Hungarian community, thermal baths, and wine-making traditions.
-
B.
Berdichev
Berdichev is a historic city in present-day Ukraine, long known as a major center of Jewish life and commerce in Eastern Europe.
-
C.
Kozelsk
Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
-
D.
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.
-
E.
Rivne
Rivne is a city in western Ukraine that serves as an important regional administrative, economic, and cultural center.
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6afc9138c81909d228ce4936d6b8b |
completed | March 27, 2026, 4:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7918c208190924c1906c7886a2c |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 1:59 p.m.