Triple
T19803441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buslovskaya |
E475745
|
entity |
| Predicate | railwayBorderControl |
P46215
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Buslovskaya, railwayBorderControl, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayBorderControl Context triple: [Buslovskaya, railwayBorderControl, yes]
-
A.
borderStation
chosen
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
B.
hasRailBorderCrossing
Indicates that two places are connected by at least one official border crossing that is served by rail transport.
-
C.
hasBorderRailwayStationWith
Indicates that two regions share a common border at which there is a railway station connecting or serving both sides.
-
D.
hasBorderControlRole
Indicates that an entity holds a role or responsibility related to managing, enforcing, or overseeing border control activities.
-
E.
hasBorderControlFacility
Indicates that one location possesses an official facility responsible for managing and controlling border crossings to or from another location.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654266e18819085698aed8b0e2ba8 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.