Triple
T34864246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poleshuks |
E1004968
|
entity |
| Predicate | locatedInBorderlandsOf |
P61305
|
FINISHED |
| Object | Belarus |
E13665
|
NE 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: Belarus | Statement: [Poleshuks, locatedInBorderlandsOf, Belarus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBorderlandsOf Context triple: [Poleshuks, locatedInBorderlandsOf, Belarus]
-
A.
locatedNearStateBorderWith
chosen
Indicates that one entity is situated geographically close to the border of a specified state.
-
B.
isLocatedOnOutskirtsOf
Indicates that one entity is situated on the outer edge or peripheral area of another entity, rather than in its central or inner part.
-
C.
isInBorderTown
Indicates that an entity is located in a town situated on or very near a political or geographic border.
-
D.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
E.
locatedInMiningBelt
Indicates that an entity is situated within a designated mining belt or mining region.
- F. None of above.
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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786d0ea648190a735682a87493eff |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.