Triple
T19492980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmingen-Liptingen |
E487697
|
entity |
| Predicate | isInBorderRegion |
P77476
|
FINISHED |
| Object | Germany–Switzerland border 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: Germany–Switzerland border area | Statement: [Emmingen-Liptingen, isInBorderRegion, Germany–Switzerland border area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInBorderRegion Context triple: [Emmingen-Liptingen, isInBorderRegion, Germany–Switzerland border area]
-
A.
borderIsAffectedBy
Indicates that a border’s state, condition, or characteristics are influenced or changed by another factor or event.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
borderIsInternalTo
Indicates that the boundary or border of one entity lies entirely within the interior of another entity, without crossing or extending outside it.
-
D.
isInSubregion
chosen
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
E.
borderIncludesEnclaveRegion
Indicates that a border surrounds or contains an enclave region within its boundaries.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6348f4d708190a6e612863fee4b97 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.