Triple
T21456634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grenzbrigade Küste |
E529356
|
entity |
| Predicate | guardedBorderType |
P69016
|
FINISHED |
| Object | maritime border |
—
|
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: maritime border | Statement: [Grenzbrigade Küste, guardedBorderType, maritime border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedBorderType Context triple: [Grenzbrigade Küste, guardedBorderType, maritime border]
-
A.
hadBorderType
chosen
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
B.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
C.
recognizedBorder
Indicates that one entity formally acknowledges and accepts another entity’s boundary as a legitimate border.
-
D.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
-
E.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d7af248190a3bc06a390f390bf |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:08 p.m.