Triple
T19616505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byalynichy–Horki area |
E470873
|
entity |
| Predicate | hasAdministrativeCenter |
P1474
|
FINISHED |
| Object | Byalynichy |
—
|
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: Byalynichy | Statement: [Byalynichy–Horki area, hasAdministrativeCenter, Byalynichy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Byalynichy Context triple: [Byalynichy–Horki area, hasAdministrativeCenter, Byalynichy]
-
A.
Byalynichy
chosen
Byalynichy is a small town in eastern Belarus known as an administrative center in the Mogilev Region.
-
B.
Ilyinichna
Ilyinichna is a Russian female patronymic derived from the given name Ilya, indicating "daughter of Ilya."
-
C.
Białous
Białous is a Polish surname most notably associated with Ryszard Białous, a figure linked to Poland’s 20th-century history.
-
D.
Golymin
Golymin is a village in east-central Poland best known as the site of a significant engagement during the Napoleonic Wars.
-
E.
Byazhin
Byazhin is a suburban community within Nigeria’s Federal Capital Territory, situated in the Bwari Area Council near Abuja.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e272808190800c5bccccd64753 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:43 p.m.