Triple
T30947256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitterfeld district |
E788428
|
entity |
| Predicate | postReunificationChange |
P123718
|
FINISHED |
| Object | industrial restructuring |
—
|
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: industrial restructuring | Statement: [Bitterfeld district, postReunificationChange, industrial restructuring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postReunificationChange Context triple: [Bitterfeld district, postReunificationChange, industrial restructuring]
-
A.
postReunificationCreation
Indicates that something was created or came into existence after a reunification event had taken place.
-
B.
postReunificationUse
Indicates how something is used or purposed after a reunification has taken place.
-
C.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
-
D.
reunifiedAs
Indicates that entities which were previously separated or divided have been brought back together into a single unified whole.
-
E.
statusAfterGermanReunification
chosen
Indicates the condition or state of an entity following the political reunification of Germany.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:53 p.m.