Triple
T30242965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyšné Nemecké |
E768970
|
entity |
| Predicate | borderCrossingDirectionTo |
P196783
|
FINISHED |
| Object | Ukraine eastbound |
—
|
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: Ukraine eastbound | Statement: [Vyšné Nemecké, borderCrossingDirectionTo, Ukraine eastbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingDirectionTo Context triple: [Vyšné Nemecké, borderCrossingDirectionTo, Ukraine eastbound]
-
A.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction 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.
borderCrossingArea
Indicates an area specifically designated for crossing a border between two jurisdictions or territories.
-
D.
borderCrossingMode
Indicates the means or method by which a border is crossed between territories or jurisdictions.
-
E.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: April 29, 2026, 7:39 p.m.