Triple
T7813140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin-Brandenburg border |
E180734
|
entity |
| Predicate | hasNoBorderControl |
P13728
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Berlin-Brandenburg border, hasNoBorderControl, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoBorderControl Context triple: [Berlin-Brandenburg border, hasNoBorderControl, yes]
-
A.
hasBorderControlStatus
chosen
Indicates the type or condition of border control that applies to a given entity or location.
-
B.
hasBorderControlFacility
Indicates that one location possesses an official facility responsible for managing and controlling border crossings to or from another location.
-
C.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
D.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
E.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78f3d6481909841d64117f657e1 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:38 p.m.