Triple
T34303757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heereskorps |
E880251
|
entity |
| Predicate | commandEchelon |
P11882
|
FINISHED |
| Object | intermediate between division and army |
—
|
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: intermediate between division and army | Statement: [Heereskorps, commandEchelon, intermediate between division and army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandEchelon Context triple: [Heereskorps, commandEchelon, intermediate between division and army]
-
A.
commandLevel
chosen
Indicates the hierarchical degree of authority or control one entity holds over another within a command structure.
-
B.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
C.
commandedFormation
Indicates that one entity held command authority over a specific military or organizational formation.
-
D.
escortCommander
Indicates that one entity serves as the commanding officer responsible for leading or overseeing an escort force or mission involving another entity.
-
E.
commanderPosition
Indicates that one entity holds the role or position of commander in relation to another entity.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 1:57 a.m.