Triple
T31082487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schippenbeil |
E792137
|
entity |
| Predicate | postWorldWarIIDisposition |
P5141
|
FINISHED |
| Object | transferred from Germany 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 from Germany to Poland | Statement: [Schippenbeil, postWorldWarIIDisposition, transferred from Germany to Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWorldWarIIDisposition Context triple: [Schippenbeil, postWorldWarIIDisposition, transferred from Germany to Poland]
-
A.
postWarPerception
Indicates how something is regarded, interpreted, or understood in the period following a war.
-
B.
statusAfterWWII
chosen
Indicates the condition, role, or classification an entity had following the end of World War II.
-
C.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
D.
postWarHistory
Indicates a relationship where something concerns, describes, or belongs to the historical period and events following a specific war.
-
E.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.