Triple
T19162887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohenstein in Ostpreußen |
E469101
|
entity |
| Predicate | after1945Status |
P5141
|
FINISHED |
| Object | transferred to Poland |
—
|
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: transferred to Poland | Statement: [Hohenstein in Ostpreußen, after1945Status, transferred to Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: after1945Status Context triple: [Hohenstein in Ostpreußen, after1945Status, transferred to Poland]
-
A.
statusIn1945
Indicates the condition, role, or classification an entity had specifically during the year 1945.
-
B.
statusAfter1946
Indicates the status or condition of an entity as it existed after the year 1946.
-
C.
regionAfter1945
Indicates that one region exists as the geopolitical or administrative successor of another region after the year 1945.
-
D.
statusAfterWWII
chosen
Indicates the condition, role, or classification an entity had following the end of World War II.
-
E.
statusAfter1941
Indicates the condition or state of an entity as it existed after the year 1941.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebe03ac8190bbe0b34ebf0d90c6 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.