Triple
T22475926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mösskirch |
E555629
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Mösskirch |
—
|
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: Mösskirch | Statement: [Battle of Mösskirch, location, Mösskirch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mösskirch Context triple: [Battle of Mösskirch, location, Mösskirch]
-
A.
Weiskirchen
Weiskirchen is a municipality in the Saarland region of western Germany, known for its scenic natural surroundings and spa facilities.
-
B.
Messkirch
chosen
Messkirch is a small town in southwestern Germany best known as the birthplace of philosopher Martin Heidegger.
-
C.
Mengerskirchen
Mengerskirchen is a small municipality in the Limburg-Weilburg district of Hesse, Germany, known for its rural character and historic castle.
-
D.
Sitzenkirch
Sitzenkirch is a village and district of the town of Kandern in the Lörrach district of Baden-Württemberg, Germany.
-
E.
Neuenkirch
Neuenkirch is a municipality in the canton of Lucerne in central Switzerland, known for its rural character and proximity to the city of Lucerne.
- 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_69e11e52c2048190952dc5df209b9bed |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15be3930c8190ba967196df7e083f |
completed | April 29, 2026, 1:16 a.m. |
Created at: April 16, 2026, 8:49 p.m.