Triple
T15531934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großgörschenstraße |
E370239
|
entity |
| Predicate | hasNameComponent |
P24447
|
FINISHED |
| Object |
Großgörschen
Großgörschen is a German place name, likely referring to a village or locality that lends its name to streets such as Großgörschenstraße.
|
E1174023
|
NE FINISHED |
How this triple was built (4 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: Großgörschen | Statement: [Großgörschenstraße, hasNameComponent, Großgörschen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Großgörschen Context triple: [Großgörschenstraße, hasNameComponent, Großgörschen]
-
A.
Gremsdorf
Gremsdorf is a small municipality in the Erlangen-Höchstadt district of Bavaria, Germany.
-
B.
Göhren
Göhren is a seaside resort town on the Baltic Sea coast of Germany, located on the island of Rügen and known for its beaches and tourism.
-
C.
Gieselau
Gieselau is a small river in northern Germany that serves as a tributary of the Eider.
-
D.
Züssow
Züssow is a small railway junction village in northeastern Germany that serves as a key transfer point between regional trains and the Usedomer Bäderbahn line to the Baltic Sea island of Usedom.
-
E.
Genthin
Genthin is a small town in the German state of Saxony-Anhalt, historically part of Prussia and known for its location along the Elbe–Havel Canal.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Großgörschen Triple: [Großgörschenstraße, hasNameComponent, Großgörschen]
Generated description
Großgörschen is a German place name, likely referring to a village or locality that lends its name to streets such as Großgörschenstraße.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Großgörschen Target entity description: Großgörschen is a German place name, likely referring to a village or locality that lends its name to streets such as Großgörschenstraße.
-
A.
Gremsdorf
Gremsdorf is a small municipality in the Erlangen-Höchstadt district of Bavaria, Germany.
-
B.
Göhren
Göhren is a seaside resort town on the Baltic Sea coast of Germany, located on the island of Rügen and known for its beaches and tourism.
-
C.
Gieselau
Gieselau is a small river in northern Germany that serves as a tributary of the Eider.
-
D.
Züssow
Züssow is a small railway junction village in northeastern Germany that serves as a key transfer point between regional trains and the Usedomer Bäderbahn line to the Baltic Sea island of Usedom.
-
E.
Genthin
Genthin is a small town in the German state of Saxony-Anhalt, historically part of Prussia and known for its location along the Elbe–Havel Canal.
- F. None of above. chosen
Provenance (5 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414877d88190804ee76566004e13 |
completed | April 16, 2026, 1:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82e376f08190b5ae9793a0381204 |
completed | May 9, 2026, 6:54 p.m. |
| NEDg | Description generation | batch_69ff83a48be88190b0d32c3657a596ea |
completed | May 9, 2026, 6:57 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff846436e48190b711da134c9a3b81 |
completed | May 9, 2026, 7 p.m. |
Created at: April 10, 2026, 4:06 a.m.