Triple
T29850831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS command hierarchy |
E758063
|
entity |
| Predicate | topPositionHolder |
P153638
|
FINISHED |
| Object | Heinrich Himmler |
—
|
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: Heinrich Himmler | Statement: [SS command hierarchy, topPositionHolder, Heinrich Himmler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topPositionHolder Context triple: [SS command hierarchy, topPositionHolder, Heinrich Himmler]
-
A.
topPositionHeldBy
chosen
Indicates that a particular top or highest-ranking position is occupied or held by a specific entity.
-
B.
titleHolderStartPosition
Indicates the position in a sequence or ranking at which an entity begins holding a particular title.
-
C.
topLocation
Indicates that one location is the primary, highest-level, or most prominent place associated with another entity or set of locations.
-
D.
topBoundary
Indicates that one entity serves as the uppermost limit, edge, or border of another entity or region.
-
E.
topForward
Indicates that one entity is positioned or oriented in front of and above another entity along a forward-facing direction.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67647d9f881908567463e1b38d70f |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:44 p.m.