Triple
T15502971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arrondissement of Mulhouse |
E379006
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Lutterbach
Lutterbach is a commune in the Haut-Rhin department of northeastern France, situated near the city of Mulhouse in the Grand Est region.
|
E1160960
|
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: Lutterbach | Statement: [arrondissement of Mulhouse, contains, Lutterbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lutterbach Context triple: [arrondissement of Mulhouse, contains, Lutterbach]
-
A.
Luterbach
Luterbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Aare River.
-
B.
Gentalbach
Gentalbach is a mountain stream in the Swiss Alps that flows through the Gental valley before joining the Hasli-Aare river system.
-
C.
Gaisbach
Gaisbach is a village and district of the town of Oberkirch in the state of Baden-Württemberg in southwestern Germany.
-
D.
Wielenbach
Wielenbach is a small municipality in the Upper Bavarian region of Germany, situated within the district of Weilheim-Schongau.
-
E.
Schrecksbach
Schrecksbach is a small municipality in the German state of Hesse, known for its rural character and location within the Schwalm-Eder district.
- 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: Lutterbach Triple: [arrondissement of Mulhouse, contains, Lutterbach]
Generated description
Lutterbach is a commune in the Haut-Rhin department of northeastern France, situated near the city of Mulhouse in the Grand Est region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lutterbach Target entity description: Lutterbach is a commune in the Haut-Rhin department of northeastern France, situated near the city of Mulhouse in the Grand Est region.
-
A.
Luterbach
Luterbach is a municipality in the canton of Solothurn in northwestern Switzerland, known for its residential character and proximity to the Aare River.
-
B.
Gentalbach
Gentalbach is a mountain stream in the Swiss Alps that flows through the Gental valley before joining the Hasli-Aare river system.
-
C.
Gaisbach
Gaisbach is a village and district of the town of Oberkirch in the state of Baden-Württemberg in southwestern Germany.
-
D.
Wielenbach
Wielenbach is a small municipality in the Upper Bavarian region of Germany, situated within the district of Weilheim-Schongau.
-
E.
Schrecksbach
Schrecksbach is a small municipality in the German state of Hesse, known for its rural character and location within the Schwalm-Eder district.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcc5bb88190b8a9a81419a9a38b |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3669f908819087162b1b8a4e4320 |
completed | May 9, 2026, 1:28 p.m. |
| NEDg | Description generation | batch_69ff375856448190a61979dfff751f06 |
completed | May 9, 2026, 1:32 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff382f1bbc8190810d0d825430f9ea |
completed | May 9, 2026, 1:35 p.m. |
Created at: April 10, 2026, 3:54 a.m.