Triple
T31508778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichssicherheitsdienst |
E803887
|
entity |
| Predicate | notablePersonProtected |
P7128
|
FINISHED |
| Object | Adolf Hitler |
E804
|
NE 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: Adolf Hitler | Statement: [Reichssicherheitsdienst, notablePersonProtected, Adolf Hitler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePersonProtected Context triple: [Reichssicherheitsdienst, notablePersonProtected, Adolf Hitler]
-
A.
notablePersonDiscussed
Indicates that the subject entity includes or features a discussion about the referenced notable person.
-
B.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
C.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
-
D.
notablePersonnel
chosen
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
E.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- F. None of above.
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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d78dc488190b1a22a1a31559a4e |
completed | June 11, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:48 p.m.