Triple
T25836395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genthin rail disaster of 1939 |
E650812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport disaster in Germany |
C50781
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: transport disaster in Germany Context triple: [Genthin rail disaster of 1939, instanceOf, transport disaster in Germany]
-
A.
bridge in Germany
A bridge in Germany is a structural construction that spans physical obstacles such as rivers, valleys, or roads within German territory, facilitating transportation and connectivity while often reflecting the country's engineering standards and regional architectural styles.
-
B.
settlement in Germany
A settlement in Germany is a populated place, such as a city, town, village, or hamlet, recognized within the country's administrative and geographic framework as a distinct inhabited locality.
-
C.
Organisation in Deutschland
Eine Organisation in Deutschland ist eine strukturierte, rechtlich oder faktisch anerkannte Einheit von Personen und Ressourcen, die in Deutschland mit definierten Zielen, Regeln und Zuständigkeiten dauerhaft zusammenwirkt.
-
D.
Berlin S-Bahn service
Berlin S-Bahn service is a rapid transit and suburban rail network that provides frequent, high-capacity train connections across Berlin and its surrounding metropolitan region.
-
E.
town in Germany
A town in Germany is a moderately sized, legally defined urban municipality that serves as a local administrative, economic, and cultural center within the German federal system.
- F. None of above. chosen
Provenance (1 batch)
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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:43 a.m.