Triple
T34746331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großdeutsches Reich |
E1001644
|
entity |
| Predicate | successorIdeologyRejectedBy |
P86075
|
FINISHED |
| Object | post‑war Germany |
—
|
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: post‑war Germany | Statement: [Großdeutsches Reich, successorIdeologyRejectedBy, post‑war Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorIdeologyRejectedBy Context triple: [Großdeutsches Reich, successorIdeologyRejectedBy, post‑war Germany]
-
A.
opposedSuccessor
Indicates that one entity becomes the successor of another in a context of opposition, conflict, or adversarial replacement.
-
B.
opposedPolicyOfPredecessor
chosen
Indicates that one entity actively rejected, resisted, or worked against the policies established by its predecessor.
-
C.
hasSuccessorIdeology
Indicates that one ideology follows, replaces, or develops from another as its subsequent ideological form or movement.
-
D.
successorInIdea
Indicates that one idea conceptually follows, develops from, or replaces another in a sequence of intellectual progression.
-
E.
successorCampaign
Indicates that one campaign directly follows and continues or replaces another campaign in sequence.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: May 3, 2026, 3:59 p.m.