Triple
T31044527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of the SS Race and Settlement Main Office |
E791087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | senior SS position |
C57471
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: senior SS position Context triple: [Head of the SS Race and Settlement Main Office, instanceOf, senior SS position]
-
A.
senior advisory position
A senior advisory position is a high-level role in which an experienced professional provides strategic guidance, expert insight, and informed recommendations to support decision-making within an organization or governing body.
-
B.
senior engineering position
A senior engineering position is a high-level technical role responsible for leading complex projects, making architectural decisions, mentoring other engineers, and driving engineering best practices to deliver robust, scalable solutions.
-
C.
senior clerical rank
A senior clerical rank is a high-level position within a religious or administrative hierarchy, typically involving significant authority, oversight responsibilities, and decision-making power over lower-ranking clerical roles.
-
D.
senior clerical role
A senior clerical role is a higher-level administrative position responsible for overseeing complex office tasks, ensuring accurate records and documentation, and often supervising junior clerical staff.
-
E.
senior oversight role
A senior oversight role is a high-level position responsible for monitoring, guiding, and ensuring the integrity, compliance, and strategic alignment of an organization’s activities and decisions.
- F. None of above. chosen
Provenance (1 batch)
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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.