Triple
T28323334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annaberg district |
E717335
|
entity |
| Predicate | hadBorderRiver |
P75268
|
FINISHED |
| Object | Zschopau River |
—
|
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: Zschopau River | Statement: [Annaberg district, hadBorderRiver, Zschopau River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBorderRiver Context triple: [Annaberg district, hadBorderRiver, Zschopau River]
-
A.
isOnBorderRiver
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
-
B.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
C.
hadBorder
Indicates that one entity shared a common boundary or frontier with another entity during a specified time period.
-
D.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
E.
borderRiverContext
chosen
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492ce1ec81908f51388ed8eea019 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:26 a.m.