Triple
T34475365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nedić’s Government of National Salvation |
E885017
|
entity |
| Predicate | antiRomaPolicy |
P179402
|
FINISHED |
| Object | participated in persecution of Roma |
—
|
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: participated in persecution of Roma | Statement: [Nedić’s Government of National Salvation, antiRomaPolicy, participated in persecution of Roma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiRomaPolicy Context triple: [Nedić’s Government of National Salvation, antiRomaPolicy, participated in persecution of Roma]
-
A.
stanceTowardRome
Indicates the nature or attitude of an entity’s position or policy in relation to Rome.
-
B.
rom
Indicates a romantic relationship or romantic involvement between the related entities.
-
C.
aimOfRome
Indicates that something is the goal, purpose, or intended objective of Rome.
-
D.
consideredByRomeAs
Indicates that something or someone is regarded or classified in a particular way by Rome (e.g., Roman authorities, culture, or legal system).
-
E.
interactionWithRome
Indicates a relationship in which an entity engages in some form of contact, exchange, or involvement with Rome.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 2:01 a.m.