Triple
T17452784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breslau Hauptbahnhof |
E424954
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Breslau |
—
|
NE NERFINISHED |
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: Breslau | Statement: [Breslau Hauptbahnhof, locatedIn, Breslau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Breslau Context triple: [Breslau Hauptbahnhof, locatedIn, Breslau]
-
A.
Breslau
chosen
Breslau is the historical German name for the city now known as Wrocław in southwestern Poland, a major cultural and academic center in Central Europe.
-
B.
Stettin
Stettin, now known as Szczecin, is a major port city on the Oder River in northwestern Poland near the Baltic Sea.
-
C.
Glogau
Glogau is the German name for the town of Głogów, a historic city in southwestern Poland on the Oder River.
-
D.
Oppeln
Oppeln is the historical German name for the city of Opole, a major cultural and administrative center in southwestern Poland’s Silesia region.
-
E.
Lemberg
Lemberg is a prominent mountain in the Swabian Jura of Baden-Württemberg, Germany, known as the highest peak in that range.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513faa0c8190961cf504c459bf34 |
completed | April 19, 2026, 3:51 a.m. |
Created at: April 10, 2026, 5:47 a.m.