Triple
T16919950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innsbrucker Platz |
E410418
|
entity |
| Predicate | hasNearbyDistrict |
P4647
|
FINISHED |
| Object | Friedenau |
—
|
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: Friedenau | Statement: [Innsbrucker Platz, hasNearbyDistrict, Friedenau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Friedenau Context triple: [Innsbrucker Platz, hasNearbyDistrict, Friedenau]
-
A.
Friedenau
chosen
Friedenau is a residential district in southwestern Berlin known for its historic architecture, leafy streets, and literary heritage.
-
B.
Friedensau
Friedensau is a small locality in the town of Genthin in Saxony-Anhalt, Germany, known for hosting the theological campus of Friedensau Adventist University.
-
C.
Friedenweiler
Friedenweiler is a small municipality in southwestern Germany’s Black Forest region, known for its forested landscapes and tranquil rural character.
-
D.
Heidenau
Heidenau is a small town in the German state of Saxony, located near Dresden along the Elbe River.
-
E.
Weidenau
Weidenau is a district of the city of Siegen in North Rhine-Westphalia, Germany.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 5:30 a.m.