Triple
T34950591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | regionBelarusianSide |
P107329
|
FINISHED |
| Object | Brest 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: Brest Region | Statement: [Terespol–Brest, regionBelarusianSide, Brest Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionBelarusianSide Context triple: [Terespol–Brest, regionBelarusianSide, Brest Region]
-
A.
borderingBelarusRegion
Indicates that one region shares a land border with a region located in Belarus.
-
B.
hasLanguageOnBelarusianSide
Indicates that an entity has a specified language used or displayed on the Belarusian side of a border, interface, or context.
-
C.
hasCityOnBelarusianSide
Indicates that a specified entity has a city located on the Belarusian side of a border or within Belarusian territory.
-
D.
modernBelarusianAdministrativeRegion
chosen
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
-
E.
timeZoneOnBelarusianSide
Indicates that the referenced time zone is the one used on the Belarusian side of a border, region, or context involving Belarus.
- F. None of above.
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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4 p.m.