Triple
T20368618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kulata–Promachonas border crossing |
E496984
|
entity |
| Predicate | railCheckpointFor |
P139876
|
FINISHED |
| Object | international rail traffic |
—
|
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: international rail traffic | Statement: [Kulata–Promachonas border crossing, railCheckpointFor, international rail traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railCheckpointFor Context triple: [Kulata–Promachonas border crossing, railCheckpointFor, international rail traffic]
-
A.
railPosition
Indicates the relative location or alignment of something with respect to a rail or set of rails.
-
B.
railHead
Indicates a relationship where one location serves as the terminus or primary endpoint of a railway line for another location or transport link.
-
C.
hasCheckpointControl
Indicates that one entity exercises control, management, or authority over a checkpoint associated with another entity.
-
D.
wasCheckpointName
Indicates that an entity previously had a specific checkpoint name assigned to it.
-
E.
hasCheckpointInfrastructure
Indicates that an entity possesses or is equipped with the necessary facilities, systems, or structures to support checkpoint operations.
- 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_69e0b4a4f9b081908a5a021919c21ccb |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678734b188190bb2c5863023f9f8c |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:26 a.m.