Triple
T2782976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsführer-SS |
E61738
|
entity |
| Predicate | elevatedToHighestRank |
P3787
|
FINISHED |
| Object | 1934 |
—
|
LITERAL FINISHED |
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: 1934 | Statement: [Reichsführer-SS, elevatedToHighestRank, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToHighestRank Context triple: [Reichsführer-SS, elevatedToHighestRank, 1934]
-
A.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
-
B.
formerHighest
Indicates that an entity once held the highest rank, position, or status in a given context but no longer does.
-
C.
nextHigherRank
Indicates that one entity holds the immediately superior rank or level in a hierarchy relative to another entity.
-
D.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
E.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdd00b65c8190a8ea444308c4fa2b |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.