Triple
T24341453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 13th Panzer Division |
E613522
|
entity |
| Predicate | conversionToPanzerDivision |
P155774
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [13th Panzer Division, conversionToPanzerDivision, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionToPanzerDivision Context triple: [13th Panzer Division, conversionToPanzerDivision, 1940]
-
A.
GermanArmyGroupRenamed
Indicates that a specific German army group has undergone a change of designation or name.
-
B.
germanUnit
Indicates that an entity is a military or organizational unit that belongs to, originates from, or is associated with Germany.
-
C.
rifleDivision
Indicates a military organizational relationship where an entity functions as or is assigned to a rifle division.
-
D.
GermanArmourUsed
Indicates that a piece of German armor was employed or deployed in a particular context, such as a battle, unit, or operation.
-
E.
upgradedToRegiment
Indicates that a military unit or formation has been elevated in status, size, or organizational level to become a regiment.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932511908190993ed984fdc4c739 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:57 a.m.