Triple
T25017488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Böhmerwald |
E626178
|
entity |
| Predicate | locatedAlongBorderWith |
P224
|
FINISHED |
| Object | Bavaria |
—
|
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: Bavaria | Statement: [Böhmerwald, locatedAlongBorderWith, Bavaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAlongBorderWith Context triple: [Böhmerwald, locatedAlongBorderWith, Bavaria]
-
A.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
C.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
-
D.
разположенНаГраницаМежду
Indicates that something is located on or along the boundary between two entities.
-
E.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 18, 2026, 6:06 a.m.