Triple
T1435819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahlden |
E30556
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Walsrode |
E143427
|
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: Walsrode | Statement: [Ahlden, locatedNear, Walsrode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walsrode Context triple: [Ahlden, locatedNear, Walsrode]
-
A.
Walsrode
chosen
Walsrode is a small town in Lower Saxony, Germany, known for its location in the Lüneburg Heath region and its large bird park, the Weltvogelpark Walsrode.
-
B.
Radevormwald
Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
-
C.
Hasselwerder
Hasselwerder is a small island located in Lake Tegel in Berlin, Germany.
-
D.
Weiterstadt
Weiterstadt is a town in the German state of Hesse, located near Darmstadt and known for its residential areas and commercial centers.
-
E.
Rheydt
Rheydt is a district of the German city of Mönchengladbach in North Rhine-Westphalia, historically an independent town in the Rhineland.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c50250b88190a0fcf3e0cbba0b1a |
completed | March 1, 2026, 11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3b07b688190a0c90796da21c4d5 |
completed | March 8, 2026, 10:09 p.m. |
Created at: March 1, 2026, 8 p.m.