Triple
T20747762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gänserndorf District |
E510630
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Gänserndorf-Süd |
—
|
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: Gänserndorf-Süd | Statement: [Gänserndorf District, containsSettlement, Gänserndorf-Süd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gänserndorf-Süd Context triple: [Gänserndorf District, containsSettlement, Gänserndorf-Süd]
-
A.
Gänserndorf
chosen
Gänserndorf is a town in Lower Austria that serves as a regional center on the eastern edge of the Marchfeld plain, northeast of Vienna.
-
B.
Gneixendorf
Gneixendorf is a village and cadastral community that forms part of the city of Krems an der Donau in Lower Austria.
-
C.
Rannersdorf
Rannersdorf is a village and cadastral community that forms part of the town of Schwechat in Lower Austria, near Vienna.
-
D.
Groß-Enzersdorf
Groß-Enzersdorf is a town in Lower Austria located just east of Vienna, known for its historic town center and proximity to the Danube wetlands.
-
E.
Seifhennersdorf
Seifhennersdorf is a small town in the Görlitz district of Saxony in eastern Germany, near the Czech border.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c226fbf881909794eff3ee9e206b |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:33 p.m.