Triple
T407337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leineschloss |
E9410
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Hanover |
E21642
|
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: Hanover | Statement: [Leineschloss, city, Hanover]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanover Context triple: [Leineschloss, city, Hanover]
-
A.
Hanover
chosen
Hanover is a historic city in northern Germany that served as the capital of the former Kingdom of Hanover and the ancestral seat of the British House of Hanover.
-
B.
Hamburg
Hamburg is Germany’s second-largest city and a major northern European port and cultural center on the River Elbe.
-
C.
Braunschweig
Braunschweig is a historic city in northern Germany known for its medieval architecture, cultural institutions, and role as an important economic and scientific center.
-
D.
Mitte, Hanover
Mitte, Hanover is the central district of the German city of Hanover, encompassing its historic core, main governmental buildings, and key cultural landmarks.
-
E.
Bremen
Bremen is a city-state in northwestern Germany comprising the cities of Bremen and Bremerhaven, known for its historic Hanseatic heritage and major port on the Weser River.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbd766c8190bb8a91605929156a |
completed | Feb. 28, 2026, 1:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac4bec4b688190a2fcbff37b3dfe59 |
completed | March 7, 2026, 4:01 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.