Triple
T21458242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fricktal |
E529397
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Arisdorf |
—
|
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: Arisdorf | Statement: [Fricktal, containsMunicipality, Arisdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arisdorf Context triple: [Fricktal, containsMunicipality, Arisdorf]
-
A.
Arisdorf
chosen
Arisdorf is a small municipality in the canton of Basel-Landschaft in northwestern Switzerland, known for its rural character and proximity to the city of Basel.
-
B.
Alsterdorf
Alsterdorf is a residential quarter in the Hamburg-Nord borough of Hamburg, Germany, known for its green spaces and proximity to the Alster River.
-
C.
Diedorf
Diedorf is a market town in Bavaria, Germany, located just west of the city of Augsburg.
-
D.
Pappenheim
Pappenheim is a historic market town in Bavaria, Germany, known for its medieval architecture and its location along the Altmühl River.
-
E.
Daisendorf
Daisendorf is a small municipality in the Bodenseekreis district of Baden-Württemberg in southern Germany, near Lake Constance.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ec254081909a703056022f4f45 |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:08 p.m.