Triple
T770293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandenburg Gate |
E16265
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Mitte |
E28609
|
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: Mitte | Statement: [Brandenburg Gate, locatedIn, Mitte]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mitte Context triple: [Brandenburg Gate, locatedIn, Mitte]
-
A.
Mitte
chosen
Mitte is the central district of Berlin, Germany, known as the historic core of the city and home to many major landmarks and government institutions.
-
B.
Middleton
Middleton is a village and civil parish in the English county of Norfolk, situated near the town of King’s Lynn.
-
C.
Middleton
Middleton is a town in Greater Manchester, England, historically part of Lancashire and now a residential and industrial suburb of Manchester.
-
D.
Sentrum
Sentrum is the central district of Oslo, Norway, which hosts some of the University of Oslo’s urban campus facilities.
-
E.
Stadtmitte
Stadtmitte is a central Berlin U-Bahn station serving as an important interchange and access point to the city’s historic Mitte district.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a704fb148190b203a5bdd77e961c |
completed | March 1, 2026, 8:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a66678f7ac819095eafccf44c6588e |
completed | March 3, 2026, 4:41 a.m. |
Created at: March 1, 2026, 7:37 p.m.