Triple
T21859646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generalplan Ost |
E539725
|
entity |
| Predicate | envisionedOutcome |
P102601
|
FINISHED |
| Object | German ethnic majority in Eastern Europe |
—
|
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: German ethnic majority in Eastern Europe | Statement: [Generalplan Ost, envisionedOutcome, German ethnic majority in Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envisionedOutcome Context triple: [Generalplan Ost, envisionedOutcome, German ethnic majority in Eastern Europe]
-
A.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
B.
planOutcome
chosen
Indicates the result or consequence that is expected or produced by a given plan.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
E.
missionOutcome
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63944d88190b6bd5e6ba4cc8ec1 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.