Triple
T32688184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Group F |
E835783
|
entity |
| Predicate | rankOfFirstCommander |
P165050
|
FINISHED |
| Object | Generalfeldmarschall |
—
|
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: Generalfeldmarschall | Statement: [Army Group F, rankOfFirstCommander, Generalfeldmarschall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOfFirstCommander Context triple: [Army Group F, rankOfFirstCommander, Generalfeldmarschall]
-
A.
initialCommanderRank
chosen
Indicates the military rank an individual held at the time they first assumed a commander position.
-
B.
rankOfNotableCommander
Indicates the military or organizational rank held by a notable commander associated with an entity.
-
C.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
D.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
-
E.
governmentCommanderRank
Indicates that an individual holds a specific rank within a government’s command or leadership hierarchy.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8174d8c8190a2352e6bc287abb4 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.