Triple
T7401093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipziger Platz |
E170748
|
entity |
| Predicate | borderSituation |
P12818
|
FINISHED |
| Object | lay on the boundary between East and West 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: lay on the boundary between East and West Berlin | Statement: [Leipziger Platz, borderSituation, lay on the boundary between East and West Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderSituation Context triple: [Leipziger Platz, borderSituation, lay on the boundary between East and West Berlin]
-
A.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
B.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
C.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
D.
borderRegion
chosen
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24f6b7c81908cb61395239d03a0 |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.