Triple
T4342506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roth |
E97815
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Rednitz |
E19589
|
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: Rednitz | Statement: [Roth, locatedOnRiver, Rednitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rednitz Context triple: [Roth, locatedOnRiver, Rednitz]
-
A.
Rednitz
chosen
The Rednitz is a river in Bavaria, Germany, that flows through cities such as Fürth and joins with the Pegnitz to form the Regnitz.
-
B.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
C.
Hoornaar
Hoornaar is a village in the Dutch province of South Holland, known for its rural character and traditional polder landscape.
-
D.
Nischel
Nischel is the local colloquial nickname for the large Karl Marx Monument in Chemnitz, Germany.
-
E.
Gantenbein
Gantenbein is the enigmatic, shape-shifting central figure in Max Frisch’s novel "Mein Name sei Gantenbein," through whom themes of identity, role-playing, and the fluidity of self are explored.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351878c148190b384053479d41caf |
completed | March 12, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5dba2b49c81909b7bf87672d71611 |
completed | March 14, 2026, 10:05 p.m. |
Created at: March 12, 2026, 11:14 p.m.