Triple
T24675821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Zgorzelec |
E610980
|
entity |
| Predicate | recognizesAsBorder |
P43368
|
FINISHED |
| Object | Oder–Neisse line |
—
|
NE NERFINISHED |
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: Oder–Neisse line | Statement: [Treaty of Zgorzelec, recognizesAsBorder, Oder–Neisse line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesAsBorder Context triple: [Treaty of Zgorzelec, recognizesAsBorder, Oder–Neisse line]
-
A.
recognizedBorder
chosen
Indicates that one entity formally acknowledges and accepts another entity’s boundary as a legitimate border.
-
B.
formsPartOfBorderType
Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
-
C.
usedAsBorder
Indicates that one entity functions as a boundary or dividing line for another entity.
-
D.
partiallyRecognizedBorder
Indicates that a border between two entities is acknowledged by some parties or to some extent, but lacks full or universal recognition.
-
E.
hasBorderRole
Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:04 a.m.