Triple
T17452824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breslau Hauptbahnhof |
E424954
|
entity |
| Predicate | relatedToponymChange |
P64305
|
FINISHED |
| Object | Breslau to Wrocław |
—
|
LITERAL 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 to Wrocław | Statement: [Breslau Hauptbahnhof, relatedToponymChange, Breslau to Wrocław]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToponymChange Context triple: [Breslau Hauptbahnhof, relatedToponymChange, Breslau to Wrocław]
-
A.
replacedByToponym
chosen
Indicates that one name or designation has been superseded and is now represented or referred to by a toponym (a place-based name).
-
B.
influenceOnToponymy
Indicates that one entity has affected or shaped the naming, form, or development of place names associated with another entity.
-
C.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
D.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
E.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
- F. None of above.
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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513faa0c8190961cf504c459bf34 |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.