Triple
T6227254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bezirk Berlin |
E139264
|
entity |
| Predicate | hadBorderType |
P69016
|
FINISHED |
| Object | inner German border in Berlin |
—
|
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: inner German border in Berlin | Statement: [Bezirk Berlin, hadBorderType, inner German border in Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBorderType Context triple: [Bezirk Berlin, hadBorderType, inner German border in Berlin]
-
A.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
B.
hasWaterBorderWith
Indicates that two entities share a common boundary that runs along or across a body of water, such as a river, lake, or sea.
-
C.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
-
D.
hasBorderFacilityType
Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
-
E.
recognizedBorder
Indicates that one entity formally acknowledges and accepts another entity’s boundary as a legitimate border.
- F. None of above. chosen
Provenance (4 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d686b88190a0e7e38ab52e2d4a |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:22 p.m.