Triple
T22425182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rixdorf |
E554349
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Alt-Rixdorf |
—
|
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: Alt-Rixdorf | Statement: [Rixdorf, hasAlternativeName, Alt-Rixdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alt-Rixdorf Context triple: [Rixdorf, hasAlternativeName, Alt-Rixdorf]
-
A.
Rixdorf
chosen
Rixdorf is a historic district in Berlin, Germany, known for its 18th-century Bohemian settlement and well-preserved village character within the modern city.
-
B.
Diedorf
Diedorf is a market town in Bavaria, Germany, located just west of the city of Augsburg.
-
C.
Rahnsdorf
Rahnsdorf is a lakeside locality in eastern Berlin, Germany, known for its village-like character, forests, and waterfront along the Müggelsee and nearby waterways.
-
D.
Alt-Mariendorf
Alt-Mariendorf is a Berlin U-Bahn station in the Mariendorf district that serves as the southern terminus of line U6.
-
E.
Ronsdorf
Ronsdorf is a district of the German city of Wuppertal in North Rhine-Westphalia, historically known as an independent town in the Bergisches Land region.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2c47bc81908b8265d83fa6fb65 |
completed | April 29, 2026, 1:09 a.m. |
Created at: April 16, 2026, 8:47 p.m.