Triple
T17774357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emsdorf |
E443724
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Emsdorf (German) |
—
|
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: Emsdorf (German) | Statement: [Emsdorf, hasNameInLanguage, Emsdorf (German)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emsdorf (German) Context triple: [Emsdorf, hasNameInLanguage, Emsdorf (German)]
-
A.
Emsdorf
chosen
Emsdorf is a village in the German state of Hesse, historically notable as the site of the Battle of Emsdorf during the Seven Years' War.
-
B.
Ebersdorf
Ebersdorf is a historic town in present-day Germany that once served as the capital of one of the small Reuss principalities.
-
C.
Porschdorf
Porschdorf is a village in Saxony, Germany, that forms part of the spa town and municipality of Bad Schandau in the Saxon Switzerland region.
-
D.
Friesdorf
Friesdorf is a residential subdistrict of the Bonn borough Bad Godesberg in western Germany.
-
E.
Dierdorf
Dierdorf is a surname most prominently associated with former American football player and sportscaster Dan Dierdorf.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871af4248190aed2b3bd42433771 |
completed | April 19, 2026, 7:41 a.m. |
Created at: April 10, 2026, 10:12 a.m.