Triple
T2417473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strömstad |
E52338
|
entity |
| Predicate | hasBorderRelation |
P37800
|
FINISHED |
| Object | cross-border trade with Norway |
—
|
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: cross-border trade with Norway | Statement: [Strömstad, hasBorderRelation, cross-border trade with Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderRelation Context triple: [Strömstad, hasBorderRelation, cross-border trade with Norway]
-
A.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
D.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
E.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc94eafd481909eeff689e5bf5960 |
completed | March 7, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6011e348190b6f9c038c7559289 |
completed | March 7, 2026, 6:30 a.m. |
Created at: March 6, 2026, 9:42 p.m.