Triple
T29996408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus–Ukraine border |
E762036
|
entity |
| Predicate | borderingBelarusRegion |
P196393
|
FINISHED |
| Object | Gomel Region |
—
|
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: Gomel Region | Statement: [Belarus–Ukraine border, borderingBelarusRegion, Gomel Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingBelarusRegion Context triple: [Belarus–Ukraine border, borderingBelarusRegion, Gomel Region]
-
A.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
B.
modernBelarusianAdministrativeRegion
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
-
C.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
-
D.
hasCityOnBelarusianSide
Indicates that a specified entity has a city located on the Belarusian side of a border or within Belarusian territory.
-
E.
bordersToTheEast
Indicates that one entity shares a boundary with another entity and is located directly to the east of it.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69fe30bb07d08190877539d5aa202d24 |
completed | May 8, 2026, 6:51 p.m. |
Created at: April 29, 2026, 6:40 p.m.