Triple
T29126714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratne Raion |
E738248
|
entity |
| Predicate | borderingRaion |
P107921
|
FINISHED |
| Object | Kovel Raion |
—
|
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: Kovel Raion | Statement: [Ratne Raion, borderingRaion, Kovel Raion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingRaion Context triple: [Ratne Raion, borderingRaion, Kovel Raion]
-
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.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
D.
sharesBorderWithPolishVoivodeship
Indicates that one entity has a land or water boundary directly adjoining a Polish voivodeship.
-
E.
borderingLocalGovernmentArea
chosen
Indicates that one local government area shares a common boundary with another local government area.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 28, 2026, 11:29 a.m.