Triple
T921377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Lippe |
E19891
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Detmold |
E269423
|
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: Detmold | Statement: [Principality of Lippe, capital, Detmold]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Detmold Context triple: [Principality of Lippe, capital, Detmold]
-
A.
Detmold
chosen
Detmold is a historic town in northwestern Germany that served as the capital and residence city of the former Principality of Lippe.
-
B.
Delmenhorst
Delmenhorst is a mid-sized industrial and commuter city in northwestern Germany, located near Bremen in the federal state of Lower Saxony.
-
C.
Osnabrück
Osnabrück is a historic city in Lower Saxony, Germany, known for its medieval architecture and role in the Peace of Westphalia.
-
D.
Kleve
Kleve is a historic town in western Germany near the Dutch border, known for its medieval castle and role as the former capital of the Duchy of Cleves.
-
E.
Hildesheim
Hildesheim is a historic city in northern Germany renowned for its medieval architecture and UNESCO-listed Romanesque churches.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b313cb908190ad78b3a54e4f2eb7 |
completed | March 1, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af1f642cf481908028e4947c98e29c |
completed | March 9, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:40 p.m.