Triple
T34950622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobrowniki–Berestovitsa |
E1007980
|
entity |
| Predicate | hasLanguageOnBelarusianSide |
P199987
|
FINISHED |
| Object | Belarusian |
—
|
LITERAL 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: Belarusian | Statement: [Bobrowniki–Berestovitsa, hasLanguageOnBelarusianSide, Belarusian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnBelarusianSide Context triple: [Bobrowniki–Berestovitsa, hasLanguageOnBelarusianSide, Belarusian]
-
A.
hasCityOnBelarusianSide
Indicates that a specified entity has a city located on the Belarusian side of a border or within Belarusian territory.
-
B.
hasLanguageOnEasternSide
Indicates that a specified language is used or spoken on the eastern side of a given area, boundary, or region.
-
C.
borderingBelarusRegion
Indicates that one region shares a land border with a region located in Belarus.
-
D.
hasLanguageOnNorthernSide
Indicates that a particular language is used or present on the northern side of a specified boundary, area, or object.
-
E.
nameInBelarusian
Indicates that an entity is known or referred to by a specific name in the Belarusian language.
- F. None of above. chosen
Provenance (4 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
| PDg | Predicate description generation | batch_69ff691e86d0819099fdb5eca5a95632 |
completed | May 9, 2026, 5:04 p.m. |
Created at: May 3, 2026, 4 p.m.