Triple
T15877767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bastei Bridge |
E384994
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Rathen |
E1127272
|
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: Rathen | Statement: [Bastei Bridge, near, Rathen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rathen Context triple: [Bastei Bridge, near, Rathen]
-
A.
Rathen
chosen
Rathen is a small scenic town in Saxon Switzerland, Germany, known as a gateway for hikers and tourists visiting the nearby Bastei rock formations and Elbe Sandstone Mountains.
-
B.
Rathwa
Rathwa are an indigenous Adivasi community of western India, primarily known for their distinctive cultural traditions, including Pithora ritual wall paintings and agrarian lifestyle.
-
C.
Rothaurach
Rothaurach is a village and district of the town of Roth in the Bavarian region of Middle Franconia, Germany.
-
D.
Rünthe
Rünthe is a former independent locality in North Rhine-Westphalia, Germany, that now forms part of the town of Bergkamen.
-
E.
Flerzheim
Flerzheim is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
- 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_69ffa950a890819092bc1e8895034593 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:51 a.m.