Triple
T2177055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxony-Anhalt |
E48552
|
entity |
| Predicate | reunificationStatus |
P37656
|
FINISHED |
| Object | recreated after German reunification |
—
|
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: recreated after German reunification | Statement: [Saxony-Anhalt, reunificationStatus, recreated after German reunification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reunificationStatus Context triple: [Saxony-Anhalt, reunificationStatus, recreated after German reunification]
-
A.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
B.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
C.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
-
D.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
E.
unificationPossible
Indicates that two entities can be combined or reconciled into a single, consistent representation under a shared set of constraints or rules.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc434978c8190b9c4dd8411b87f23 |
completed | March 7, 2026, 6:22 a.m. |
Created at: March 4, 2026, 7:45 p.m.