Triple
T29819999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland–Belarus border |
E757218
|
entity |
| Predicate | nonEUCountryOnOneSide |
P167902
|
FINISHED |
| Object | Belarus |
—
|
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: Belarus | Statement: [Poland–Belarus border, nonEUCountryOnOneSide, Belarus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonEUCountryOnOneSide Context triple: [Poland–Belarus border, nonEUCountryOnOneSide, Belarus]
-
A.
countryOnOneSide
Indicates that one entity is located on one side or border of a specified country.
-
B.
countryOnAxisSide
Indicates that a country was aligned with or belonged to the Axis side in a particular conflict or war.
-
C.
borderingCountryOnOtherSide
Indicates that one country lies on the opposite side of a shared border relative to another country.
-
D.
areLandlockedTogether
Indicates that the entities share the condition of being landlocked, with no direct access to the sea or ocean.
-
E.
betweenCountry
Indicates a relationship or interaction that involves or occurs among two or more countries.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6756645d48190a1645d578759dccd |
completed | May 2, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 29, 2026, 5:28 p.m.