Triple
T6213091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lippe |
E138916
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Lemgo |
E357782
|
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: Lemgo | Statement: [Lippe, hasMajorTown, Lemgo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lemgo Context triple: [Lippe, hasMajorTown, Lemgo]
-
A.
Lemgo
chosen
Lemgo is a historic town in the Lippe district of North Rhine-Westphalia, Germany, known for its well-preserved medieval architecture and Hanseatic heritage.
-
B.
Meppen
Meppen is a historic town in Lower Saxony, Germany, known as a regional center in the Emsland district near the Dutch border.
-
C.
Lohmar
Lohmar is a town in the Rhein-Sieg district of North Rhine-Westphalia, Germany, situated near Cologne and known for its green surroundings and residential character.
-
D.
Andernach
Andernach is a historic German town on the Rhine River in Rhineland-Palatinate, known for its medieval architecture and one of the world’s highest cold-water geysers.
-
E.
Boppard
Boppard is a historic town on the Rhine River in Germany, renowned for its well-preserved medieval architecture, wine culture, and scenic river landscapes.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0628c52ec8190b9c62c7fdc0aa83b |
completed | March 22, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c934b54a7c81909cdccd01af24c73d |
completed | March 29, 2026, 2:18 p.m. |
Created at: March 22, 2026, 4:21 p.m.