Triple
T38557191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberbefehlshaber Heeresgruppe Süd |
E925277
|
entity |
| Predicate | typeOfFormationCommanded |
P132410
|
FINISHED |
| Object | army group |
—
|
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: army group | Statement: [Oberbefehlshaber Heeresgruppe Süd, typeOfFormationCommanded, army group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFormationCommanded Context triple: [Oberbefehlshaber Heeresgruppe Süd, typeOfFormationCommanded, army group]
-
A.
commandedFormationType
chosen
Indicates the specific type of formation that an entity is ordered or directed to assume or maintain.
-
B.
commandedFormation
Indicates that one entity held command authority over a specific military or organizational formation.
-
C.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
-
D.
militaryFormationOf
Indicates that one entity is a military unit or formation that is organizationally part of, or derived from, another entity.
-
E.
navalFormation
Indicates a relationship where multiple naval units are organized into a coordinated tactical or operational group.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.