Triple
T32846821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusatian Neisse |
E840120
|
entity |
| Predicate | post1945Role |
P175175
|
FINISHED |
| Object | part of the German–Polish frontier established after World War II |
—
|
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: part of the German–Polish frontier established after World War II | Statement: [Lusatian Neisse, post1945Role, part of the German–Polish frontier established after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: post1945Role Context triple: [Lusatian Neisse, post1945Role, part of the German–Polish frontier established after World War II]
-
A.
post1945Event
Indicates that an event occurred after the year 1945.
-
B.
regionAfter1945
Indicates that one region exists as the geopolitical or administrative successor of another region after the year 1945.
-
C.
statusIn1945
Indicates the condition, role, or classification an entity had specifically during the year 1945.
-
D.
roleIn1950
Indicates that an entity held a particular role, position, or function in the year 1950.
-
E.
statusAfter1946
Indicates the status or condition of an entity as it existed after the year 1946.
- F. None of above. chosen
Provenance (4 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:16 a.m.