Triple
T34864323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medyka–Shehyni |
E1004969
|
entity |
| Predicate | borderCrossingSide |
P149547
|
FINISHED |
| Object | Polish border guard facilities |
—
|
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: Polish border guard facilities | Statement: [Medyka–Shehyni, borderCrossingSide, Polish border guard facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingSide Context triple: [Medyka–Shehyni, borderCrossingSide, Polish border guard facilities]
-
A.
borderCrossingDirectionTo
Indicates the direction in which a border crossing occurs from one side or territory to another.
-
B.
borderCrossingStatus
Indicates the current state or outcome of an entity’s attempt to cross a border (e.g., allowed, denied, pending, or completed).
-
C.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
D.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
E.
hasBorderCrossingSide
chosen
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.