Triple
T3007703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endlösung der Judenfrage |
E81940
|
entity |
| Predicate | formalCoordinationDate |
P44625
|
FINISHED |
| Object | 20 January 1942 |
—
|
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: 20 January 1942 | Statement: [Endlösung der Judenfrage, formalCoordinationDate, 20 January 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalCoordinationDate Context triple: [Endlösung der Judenfrage, formalCoordinationDate, 20 January 1942]
-
A.
formalizationDate
Indicates the date on which something is officially established, formalized, or brought into an official or legally recognized form.
-
B.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
C.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
D.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
E.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4a12508190a48ae1c86233d25e |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.