Triple
T30058190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Schaub |
E763792
|
entity |
| Predicate | personalAdjutantOf |
P154343
|
FINISHED |
| Object | Adolf Hitler |
—
|
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: Adolf Hitler | Statement: [Julius Schaub, personalAdjutantOf, Adolf Hitler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalAdjutantOf Context triple: [Julius Schaub, personalAdjutantOf, Adolf Hitler]
-
A.
adjutantIsPersonalAideOf
chosen
Indicates that one entity serves as the personal aide or assistant to another entity, typically in a formal or official capacity.
-
B.
hasAdjutant
Indicates that one entity serves as an adjutant (assistant or deputy) to another entity.
-
C.
chiefLieutenantOf
Indicates that one person serves as the primary subordinate or top-ranking assistant to another leader or authority figure.
-
D.
deputyOf
Indicates that one entity serves as the subordinate or second-in-command to another, acting with delegated authority on their behalf.
-
E.
appointedUnder
Indicates that one entity was formally given a position, role, or responsibility according to the authority, rules, or provisions established by another entity or legal framework.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 6:57 p.m.