Triple
T10701854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army corps of the Wehrmacht Heer |
E252295
|
entity |
| Predicate | typicallyCommands |
P86670
|
FINISHED |
| Object | infantry divisions |
—
|
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: infantry divisions | Statement: [Army corps of the Wehrmacht Heer, typicallyCommands, infantry divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyCommands Context triple: [Army corps of the Wehrmacht Heer, typicallyCommands, infantry divisions]
-
A.
typicalCommands
chosen
Indicates that the associated entity commonly issues or uses the specified commands as part of its normal or expected behavior.
-
B.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
C.
typicallyCommandsSize
Indicates that one entity normally determines or specifies the size or magnitude of another entity.
-
D.
commandsThrough
Indicates that one entity exercises authority or control over another indirectly, acting through an intermediary or chain of command.
-
E.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8c835c8190bf1a67ee94195926 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.