Triple
T25299027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jews in Estonia |
E634295
|
entity |
| Predicate | persecutionStartApproximate |
P99431
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Jews in Estonia, persecutionStartApproximate, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: persecutionStartApproximate Context triple: [Jews in Estonia, persecutionStartApproximate, 1941]
-
A.
persecutionBegan
chosen
Indicates that the act or process of persecuting a target started at a specific point in time.
-
B.
persecutionHistory
Indicates that an entity has experienced, participated in, or is otherwise associated with acts of persecution in the past.
-
C.
persecutedDuring
Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
-
D.
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.
-
E.
persecutedAfter
Indicates that one entity is subjected to persecution by another entity after a specified event or point in time.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd5621481909935d022d9275194 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.