Triple
T35037840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Panzer Division |
E1010977
|
entity |
| Predicate | reorganizedAsPanzerDivision |
P155774
|
FINISHED |
| Object | 1939 |
—
|
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: 1939 | Statement: [5th Panzer Division, reorganizedAsPanzerDivision, 1939]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganizedAsPanzerDivision Context triple: [5th Panzer Division, reorganizedAsPanzerDivision, 1939]
-
A.
conversionToPanzerDivision
chosen
Indicates that a military unit is reorganized or transformed into a panzer (armored) division.
-
B.
GermanArmyGroupRenamed
Indicates that a specific German army group has undergone a change of designation or name.
-
C.
GermanArmyGroup
Indicates that an entity is a specific army group belonging to or associated with the German military.
-
D.
Oberkommando
Indicates a command relationship in which a supreme or high-level military headquarters exercises overall authority and control over subordinate forces or operations.
-
E.
germanUnit
Indicates that an entity is a military or organizational unit that belongs to, originates from, or is associated with Germany.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858cb6608190a0c2fa79c2d215a6 |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.