Triple
T34950562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | hasCityOnBelarusianSide |
P186989
|
FINISHED |
| Object | Brest |
—
|
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 | Statement: [Terespol–Brest, hasCityOnBelarusianSide, Brest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityOnBelarusianSide Context triple: [Terespol–Brest, hasCityOnBelarusianSide, Brest]
-
A.
hasCityOnPolishSide
Indicates that a given entity has a city located on the Polish side of a border or within Polish territory.
-
B.
borderedOnSovietSide
Indicates that one entity shared a border specifically with the Soviet-controlled side of another entity or region.
-
C.
modernBelarusianAdministrativeRegion
Indicates that an entity is an administrative region within the contemporary state structure of Belarus.
-
D.
hasCapitalOnBorderingCountry
Indicates that the capital city of one country is located on the border it shares with another country.
-
E.
hasCountryOnBothBanks
Indicates that a river or waterway has the same country located on both of its banks along the relevant segment.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4 p.m.