Triple
T20429448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowogródek |
E501089
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Novogrudok |
—
|
NE NERFINISHED |
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: Novogrudok | Statement: [Nowogródek, alternativeName, Novogrudok]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Novogrudok Context triple: [Nowogródek, alternativeName, Novogrudok]
-
A.
Novogrudok
chosen
Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
-
B.
Zhlobin
Zhlobin is an industrial city in southeastern Belarus, known especially for its major steel production facilities and location on the Dnieper River.
-
C.
Babruysk
Babruysk is a historic city in eastern Belarus known as a former major Jewish cultural center and regional industrial hub.
-
D.
Horodnia
Horodnia is a small town in northern Ukraine known for its historical roots and location within the Chernihiv region.
-
E.
Novopolotsk
Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67bac39288190b294b291301ac843 |
completed | April 20, 2026, 7:17 p.m. |
Created at: April 16, 2026, 11:31 a.m.