Triple
T23333761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroregion Elbe/Labe |
E591516
|
entity |
| Predicate | hasCrossBorderCenter |
P151901
|
FINISHED |
| Object | Pirna |
—
|
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: Pirna | Statement: [Euroregion Elbe/Labe, hasCrossBorderCenter, Pirna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pirna Context triple: [Euroregion Elbe/Labe, hasCrossBorderCenter, Pirna]
-
A.
Pirna
chosen
Pirna is a historic town in eastern Germany situated on the River Elbe, known as a gateway to the Saxon Switzerland National Park.
-
B.
Velké Poříčí
Velké Poříčí is a municipality and village in the Hradec Králové Region of the Czech Republic, situated near the town of Náchod close to the Polish border.
-
C.
Orlice
Orlice is a river in the Czech Republic that flows through the city of Hradec Králové and is a tributary of the Labe (Elbe) River.
-
D.
Löcknitz
Löcknitz is a river in eastern Germany that flows through Brandenburg and is associated with the town of Erkner.
-
E.
Irsch
Irsch is a village and municipality in the Trier-Saarburg district of Rhineland-Palatinate in western Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197efd98c819083635a2b8440f3eb |
completed | April 29, 2026, 5:32 a.m. |
Created at: April 17, 2026, 5:16 p.m.