Triple
T32144452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reich presidency |
E820989
|
entity |
| Predicate | deFactoMergedWith |
P7838
|
FINISHED |
| Object | office of Reich Chancellor |
—
|
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: office of Reich Chancellor | Statement: [Reich presidency, deFactoMergedWith, office of Reich Chancellor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoMergedWith Context triple: [Reich presidency, deFactoMergedWith, office of Reich Chancellor]
-
A.
demergedInto
Indicates that an entity has been split or separated into one or more distinct successor entities as a result of a demerger process.
-
B.
foundedByMergerOf
Indicates that an entity was created through the merger or combination of two or more predecessor entities.
-
C.
brandMergedWith
Indicates that two previously distinct brands have combined into a single unified brand entity, typically through merger or acquisition.
-
D.
wasUnifiedWith
chosen
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
E.
governingBodyAtMerger
Indicates the organization or authority that served as the governing body of an entity at the time it merged with another entity.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9b17d908190a6bfa2f8b5402f1e |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:31 a.m.