Triple
T23910716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich Himmler (as adjutant) |
E601930
|
entity |
| Predicate | hasAdjutant |
P154342
|
FINISHED |
| Object | Joachim Peiper |
—
|
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: Joachim Peiper | Statement: [Heinrich Himmler (as adjutant), hasAdjutant, Joachim Peiper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjutant Context triple: [Heinrich Himmler (as adjutant), hasAdjutant, Joachim Peiper]
-
A.
hadSecondInCommand
Indicates that one entity had another entity serving as its second-in-command or primary subordinate leader.
-
B.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
C.
hasSergeantAtArms
Indicates that an organization, body, or group is associated with and formally appoints a specific individual to serve in the role of Sergeant-at-Arms.
-
D.
hasMilitaryAdvisor
Indicates that one entity serves as a military advisor to another, providing guidance or expertise on military matters.
-
E.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
- F. None of above. chosen
Provenance (4 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce94f65c8190807723344fa0b837 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:38 p.m.