Triple
T2073706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of Army Group A |
E44872
|
entity |
| Predicate | commandStructureLevel |
P11882
|
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: [Commander of Army Group A, commandStructureLevel, army group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandStructureLevel Context triple: [Commander of Army Group A, commandStructureLevel, army group]
-
A.
commandLevel
chosen
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
-
B.
hasCommandStructure
Indicates that one entity possesses an organized hierarchy of authority or control that governs another entity or set of entities.
-
C.
typicalCommandLevel
Indicates the usual or standard level of authority or access at which a command is intended to be executed.
-
D.
commandScope
Indicates that one entity defines or limits the range, context, or extent within which another entity’s command or control is valid or applicable.
-
E.
configurationLevel
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba101c008190840763d2f28fa8d7 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.