Triple
T15615069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thälmann Battalion |
E375390
|
entity |
| Predicate | veteransLater |
P119438
|
FINISHED |
| Object | persecuted in Nazi Germany |
—
|
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: persecuted in Nazi Germany | Statement: [Thälmann Battalion, veteransLater, persecuted in Nazi Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veteransLater Context triple: [Thälmann Battalion, veteransLater, persecuted in Nazi Germany]
-
A.
isVeteranOf
Indicates that an entity has previously served in and been discharged from a specified military conflict, campaign, or armed force.
-
B.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
C.
spentLaterLifeAt
Indicates that an individual resided, worked, or was primarily based at a particular place during the later period of their life.
-
D.
usedAfterWar
Indicates that an entity came into use only after a specific war or conflict had ended.
-
E.
yearsOfMilitaryService
Indicates the number of years an entity has served or is recorded as serving in the military.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e83407c8190abbcd4b7fab0ff85 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.