Triple
T15877768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bastei Bridge |
E384994
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Pirna |
E76192
|
NE 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: Pirna | Statement: [Bastei Bridge, near, Pirna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pirna Context triple: [Bastei Bridge, near, 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.
Krzna
Krzna is a river in eastern Poland that flows through the Lublin region before joining the Bug River.
-
E.
Jauru
Jauru is an alternative name for the Yawuru, an Aboriginal Australian people traditionally associated with the Broome region of Western Australia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e155fec9d4819081efea504e1e3952 |
completed | April 16, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb59f979c8190826e35a16e295704 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 4:51 a.m.