Triple
T28356810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haltingen |
E718251
|
entity |
| Predicate | locatedInBorderTriangle |
P92622
|
FINISHED |
| Object | Dreiländereck Germany–France–Switzerland |
—
|
NE NERFINISHED |
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: Dreiländereck Germany–France–Switzerland | Statement: [Haltingen, locatedInBorderTriangle, Dreiländereck Germany–France–Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBorderTriangle Context triple: [Haltingen, locatedInBorderTriangle, Dreiländereck Germany–France–Switzerland]
-
A.
borderTriangle
chosen
Indicates that one entity is a triangular region or shape that forms part of the boundary or border of another entity.
-
B.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
C.
hasBorderTripoint
Indicates that three distinct borders or regions meet at a single common point.
-
D.
nearBorderBetween
Indicates that something is located close to the dividing line or boundary shared between two adjacent areas or regions.
-
E.
разположенНаГраницаМежду
Indicates that something is located on or along the boundary between two 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: April 28, 2026, 12:49 a.m.