Triple
T34950582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | isEUExternalBorder |
P109217
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Terespol–Brest, isEUExternalBorder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEUExternalBorder Context triple: [Terespol–Brest, isEUExternalBorder, true]
-
A.
isSchengenExternalBorder
chosen
Indicates that a given border segment functions as an external boundary between the Schengen Area and non-Schengen territories.
-
B.
isNATOExternalBorder
Indicates that a location or boundary lies on the outer edge of NATO territory, forming part of NATO’s external border with non-member areas.
-
C.
граничитСтранаЕС
Indicates that a country shares a land or maritime border with a member state of the European Union.
-
D.
EUInternalBorder
Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
-
E.
isCustomsBorderOf
Indicates that one entity serves as the official customs boundary for another, where customs controls and regulations are applied between them.
- 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_69f782cd7f4c819099f01e462863be2f |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.