Triple
T8583542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest ghettos |
E203243
|
entity |
| Predicate | typeOfPersecution |
P13133
|
FINISHED |
| Object | racial persecution |
—
|
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: racial persecution | Statement: [Budapest ghettos, typeOfPersecution, racial persecution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPersecution Context triple: [Budapest ghettos, typeOfPersecution, racial persecution]
-
A.
causeOfPersecution
Indicates that one entity is the reason or basis for another entity being persecuted.
-
B.
persecutionOf
Indicates the act of subjecting an entity to persistent, often unjust hostility, harassment, or oppression, typically on the basis of identity, beliefs, or group membership.
-
C.
methodOfPersecution
chosen
Indicates the specific means, technique, or process by which an act of persecution is carried out.
-
D.
persecutedIn
Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
-
E.
wasPersecutedBy
Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1ecc188190bbe2ab8d2423505b |
completed | March 31, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:22 p.m.