Triple
T35229394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalotina–Gradina border crossing |
E1017185
|
entity |
| Predicate | isGatewayOnCorridorLinking |
P163431
|
FINISHED |
| Object | Central Europe with Istanbul |
—
|
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: Central Europe with Istanbul | Statement: [Kalotina–Gradina border crossing, isGatewayOnCorridorLinking, Central Europe with Istanbul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGatewayOnCorridorLinking Context triple: [Kalotina–Gradina border crossing, isGatewayOnCorridorLinking, Central Europe with Istanbul]
-
A.
isGatewayCorridorFor
chosen
Indicates that something serves as a primary access route or passageway enabling movement or connection to another place, system, or area.
-
B.
isStopOnCorridor
Indicates that a location functions as a designated stop situated along a corridor or route.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
linkedByCorridor
Indicates that two locations are directly connected to each other by a corridor.
-
E.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.