Triple
T32594943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilde Sau tactic |
E833176
|
entity |
| Predicate | commanderAssociatedWith |
P1197
|
FINISHED |
| Object | Hajo Herrmann |
—
|
NE NERFINISHED |
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: Hajo Herrmann | Statement: [Wilde Sau tactic, commanderAssociatedWith, Hajo Herrmann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderAssociatedWith Context triple: [Wilde Sau tactic, commanderAssociatedWith, Hajo Herrmann]
-
A.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
-
B.
commanderAffiliation
Indicates that a commander is formally associated with, belongs to, or serves under a particular organization, group, or side.
-
C.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
D.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
-
E.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:05 a.m.