Triple
T22343857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesstraße 202 |
E552340
|
entity |
| Predicate | connectsTown |
P845
|
FINISHED |
| Object | Rendsburg |
—
|
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: Rendsburg | Statement: [Bundesstraße 202, connectsTown, Rendsburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rendsburg Context triple: [Bundesstraße 202, connectsTown, Rendsburg]
-
A.
Rendsburg
chosen
Rendsburg is a historic town in northern Germany known for its strategic location on the Kiel Canal and its distinctive high railway bridge.
-
B.
Friedrichstadt
Friedrichstadt is a historic canal town in northern Germany’s Schleswig-Holstein, known for its Dutch-style architecture and waterways.
-
C.
Barnstorf
Barnstorf is a small municipality in Lower Saxony, Germany, known for its rural character and location within the Diepholz district.
-
D.
Eidelstedt
Eidelstedt is a district in the northwestern part of Hamburg, Germany, known for its residential areas and local shopping centers.
-
E.
Sonderburg
Sonderburg is a historic town in southern Denmark, located on the island of Als and known for its strategic position and castle on the Alssund strait.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15796b2288190b10e9402abf35fd3 |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:43 p.m.