Triple
T23028170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lannesdorf |
E573380
|
entity |
| Predicate | hasNeighbouringDistrict |
P17964
|
FINISHED |
| Object | Gimmersdorf |
—
|
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: Gimmersdorf | Statement: [Lannesdorf, hasNeighbouringDistrict, Gimmersdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gimmersdorf Context triple: [Lannesdorf, hasNeighbouringDistrict, Gimmersdorf]
-
A.
Gimmersdorf
chosen
Gimmersdorf is a small village that forms one of the local subdivisions of the municipality of Wachtberg in Germany.
-
B.
Seifhennersdorf
Seifhennersdorf is a small town in the Görlitz district of Saxony in eastern Germany, near the Czech border.
-
C.
Kremsdorf
Kremsdorf is a locality within the Austrian town of Ansfelden in the state of Upper Austria.
-
D.
Althüttendorf
Althüttendorf is a small rural municipality in the Barnim district of Brandenburg in northeastern Germany.
-
E.
Gänserndorf
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.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847f453881909a8f2affb48c64f1 |
completed | April 29, 2026, 4:09 a.m. |
Created at: April 17, 2026, 3:52 p.m.