Triple
T33467086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 18th Panzer Division |
E857081
|
entity |
| Predicate | roleInOperationBarbarossa |
P16542
|
FINISHED |
| Object | armored spearhead unit |
—
|
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: armored spearhead unit | Statement: [18th Panzer Division, roleInOperationBarbarossa, armored spearhead unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInOperationBarbarossa Context triple: [18th Panzer Division, roleInOperationBarbarossa, armored spearhead unit]
-
A.
roleInOperationWeserübung
Indicates the specific role or function an entity held in the context of Operation Weserübung.
-
B.
roleInOperationOverlord
Indicates that an entity participated in Operation Overlord in a specific capacity or function.
-
C.
roleAtStalingrad
Indicates the specific role, position, or function an entity held in relation to the Battle of Stalingrad.
-
D.
roleInOperationReinhard
Indicates that an entity held a specific role or participated in some capacity in Operation Reinhard, the Nazi plan to exterminate Jews in occupied Poland during the Holocaust.
-
E.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: May 1, 2026, 1:37 a.m.