Triple
T7813098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin-Brandenburg border |
E180734
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative boundary |
C1361
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: administrative boundary Context triple: [Berlin-Brandenburg border, instanceOf, administrative boundary]
-
A.
political boundary
chosen
A political boundary is an officially recognized dividing line that separates the geographic areas of different political entities, such as countries, states, or municipalities, defining the limits of their jurisdiction and authority.
-
B.
geographical boundary
A geographical boundary is a defined line or zone on the Earth's surface that separates distinct political, cultural, or natural regions.
-
C.
international-free subnational boundary
An international-free subnational boundary is an internal administrative or political division within a country that does not coincide with or directly border any international boundary.
-
D.
land border
A land border is a defined line on the Earth's surface that separates the territories of two adjacent states or regions across contiguous land.
-
E.
boundary review
A boundary review is a systematic evaluation and adjustment of geographic or organizational limits to ensure they remain fair, effective, and fit for current and future needs.
- F. None of above.
Provenance (1 batch)
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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:38 p.m.