Triple
T35690537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubľa |
E1031275
|
entity |
| Predicate | isKeyBorderCrossing |
P170621
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ubľa, isKeyBorderCrossing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyBorderCrossing Context triple: [Ubľa, isKeyBorderCrossing, true]
-
A.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
B.
isMajorBorderCrossing
chosen
Indicates that a location or route serves as a primary, high-traffic crossing point between two bordering regions or countries.
-
C.
isCrossBorder
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
D.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
-
E.
hasBorderCrossingFunction
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.