Triple
T34564426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnus Hirschfeld |
E887431
|
entity |
| Predicate | archiveDestroyedBy |
P188466
|
FINISHED |
| Object | Nazis |
—
|
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: Nazis | Statement: [Magnus Hirschfeld, archiveDestroyedBy, Nazis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archiveDestroyedBy Context triple: [Magnus Hirschfeld, archiveDestroyedBy, Nazis]
-
A.
archivesLost
Indicates that previously existing records or documents have been lost or are no longer accessible.
-
B.
archiveBuriedAt
Indicates that an archive is located or stored at a specific buried or underground place.
-
C.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
-
D.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
E.
destroyedAfter
Indicates that one entity is destroyed at a point in time that occurs after the destruction of another entity.
- F. None of above. chosen
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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 1, 2026, 2:02 a.m.