Triple
T14019598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Unna |
E337292
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Fröndenberg |
E456760
|
NE FINISHED |
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: Fröndenberg | Statement: [district of Unna, contains, Fröndenberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fröndenberg Context triple: [district of Unna, contains, Fröndenberg]
-
A.
Fröndenberg
chosen
Fröndenberg is a small town in North Rhine-Westphalia, Germany, situated on the Ruhr River and known for its scenic rural surroundings.
-
B.
Gödringen
Gödringen is a village and district of the town of Sarstedt in Lower Saxony, Germany.
-
C.
Burgstädt
Burgstädt is a small town in the German state of Saxony, known for its traditional architecture and location near the city of Chemnitz.
-
D.
Hademstorf
Hademstorf is a small municipality in Lower Saxony, Germany, situated in the Heidekreis district.
-
E.
Radevormwald
Radevormwald is a small historic town in North Rhine-Westphalia, western Germany, known for its hilly Bergisches Land landscape and traditional textile and metalworking industries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3c7cd88190b236382058581740 |
completed | April 14, 2026, 12:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bb227b48190bed1d19b8066b283 |
completed | May 8, 2026, 3:42 a.m. |
Created at: April 9, 2026, 10:19 p.m.