Triple
T3371423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovakia–Germany border |
E70962
|
entity |
| Predicate | isExternalBorderOf |
P41826
|
FINISHED |
| Object | neither EU nor Schengen Area |
—
|
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: neither EU nor Schengen Area | Statement: [Slovakia–Germany border, isExternalBorderOf, neither EU nor Schengen Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExternalBorderOf Context triple: [Slovakia–Germany border, isExternalBorderOf, neither EU nor Schengen Area]
-
A.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
B.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
C.
isExternalTo
chosen
Indicates that one entity exists or operates outside the boundaries, scope, or domain of another entity.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2bc9bc881908b22edd631a1c110 |
completed | March 8, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.