Triple
T14495608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnsberg |
E359488
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object |
Oeventrop
Oeventrop is a village and district of the city of Arnsberg in North Rhine-Westphalia, Germany, situated in the Sauerland region.
|
E1103670
|
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: Oeventrop | Statement: [Arnsberg, hasSubdivision, Oeventrop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oeventrop Context triple: [Arnsberg, hasSubdivision, Oeventrop]
-
A.
Opoeteren
Opoeteren is a village in the Belgian province of Limburg that now forms part of the municipality of Maaseik.
-
B.
Everschop
Everschop was a former historical region or administrative unit that later became part of the Eiderstedt peninsula in northern Germany.
-
C.
Oppeano
Oppeano is a municipality in northern Italy’s Veneto region, historically associated with the ancient Veneti people.
-
D.
Krolloper
Krolloper was a historic Berlin theater and opera house known for its innovative productions and its role as the meeting place of the Reichstag during the Weimar Republic.
-
E.
Overschie
Overschie is a historic neighborhood and former village now incorporated into the city of Rotterdam in the Netherlands.
- 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: Oeventrop Triple: [Arnsberg, hasSubdivision, Oeventrop]
Generated description
Oeventrop is a village and district of the city of Arnsberg in North Rhine-Westphalia, Germany, situated in the Sauerland region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Oeventrop Target entity description: Oeventrop is a village and district of the city of Arnsberg in North Rhine-Westphalia, Germany, situated in the Sauerland region.
-
A.
Opoeteren
Opoeteren is a village in the Belgian province of Limburg that now forms part of the municipality of Maaseik.
-
B.
Everschop
Everschop was a former historical region or administrative unit that later became part of the Eiderstedt peninsula in northern Germany.
-
C.
Oppeano
Oppeano is a municipality in northern Italy’s Veneto region, historically associated with the ancient Veneti people.
-
D.
Krolloper
Krolloper was a historic Berlin theater and opera house known for its innovative productions and its role as the meeting place of the Reichstag during the Weimar Republic.
-
E.
Overschie
Overschie is a historic neighborhood and former village now incorporated into the city of Rotterdam in the Netherlands.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de93109cb081909a6e846db23a4635 |
completed | April 14, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d9731588190b27a826582e5fc6d |
completed | May 8, 2026, 4:59 a.m. |
| NEDg | Description generation | batch_69fd6f80e3a081908c43915275898852 |
completed | May 8, 2026, 5:07 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd7016a3c48190a1ea2fefeea92c60 |
completed | May 8, 2026, 5:09 a.m. |
Created at: April 10, 2026, 1:21 a.m.