Triple
T1435859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Breslau |
E30558
|
entity |
| Predicate | signedIn |
P441
|
FINISHED |
| Object | Breslau |
E238097
|
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: Breslau | Statement: [Treaty of Breslau, signedIn, Breslau]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Breslau Context triple: [Treaty of Breslau, signedIn, 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.
Oppeln
Oppeln is the historical German name for the city of Opole, a major cultural and administrative center in southwestern Poland’s Silesia region.
-
C.
Frankfurt (Oder)
Frankfurt (Oder) is a German city on the Oder River at the Polish border, known as a historic university and trade center in the state of Brandenburg.
-
D.
Dresden
Dresden is a historic cultural and economic center in eastern Germany, renowned for its baroque architecture, art collections, and reconstruction after World War II.
-
E.
Görlitz
Görlitz is a historic city in eastern Germany on the Lusatian Neisse River, known for its well-preserved old town and role as a popular film location.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c50250b88190a0fcf3e0cbba0b1a |
completed | March 1, 2026, 11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae58a7b1fc8190b76b09e64097b881 |
completed | March 9, 2026, 5:20 a.m. |
Created at: March 1, 2026, 8 p.m.