Triple
T30293714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnhem region |
E770455
|
entity |
| Predicate | hasCrossBorderFunction |
P10963
|
FINISHED |
| Object | gateway to Germany |
—
|
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: gateway to Germany | Statement: [Arnhem region, hasCrossBorderFunction, gateway to Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderFunction Context triple: [Arnhem region, hasCrossBorderFunction, gateway to Germany]
-
A.
hasCrossBorderArea
Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
-
B.
hasBorderCrossingFunction
chosen
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
C.
hasCrossBorderInteraction
Indicates that there is an interaction, activity, or relationship occurring between entities located in different countries or jurisdictions.
-
D.
isCrossBorder
Indicates that the relationship or action involves entities located in or spanning across different national or jurisdictional boundaries.
-
E.
hasCrossBorderIntegration
Indicates that there is a coordinated linkage or interaction that spans across national or jurisdictional borders between the related entities.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 7:47 p.m.