Triple
T23803070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of the Army Command of the Reichswehr |
E589624
|
entity |
| Predicate | Hans von Seeckt_termStart |
P153611
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Chief of the Army Command of the Reichswehr, Hans von Seeckt_termStart, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Hans von Seeckt_termStart Context triple: [Chief of the Army Command of the Reichswehr, Hans von Seeckt_termStart, 1920]
-
A.
commanderOfLuftwaffe
Indicates that one entity serves as the commanding officer or leader of the Luftwaffe (the German air force).
-
B.
PrussianCommander
Indicates that an individual holds the position or role of a commander within the Prussian military forces.
-
C.
notableCommanderAxis
Indicates that the subject entity had a notable military commander role or position on the Axis side in a conflict or war.
-
D.
commanderDuringWorldWarII
Indicates that one entity served as a commander of the other specifically during the period of World War II.
-
E.
germanCommander
Indicates that the subject serves as a military commander for German forces in relation to the object.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c74f34108190b11961d634559d2b |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:54 p.m.