Triple
T23953999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomainia |
E603727
|
entity |
| Predicate | hasPersecutedGroup |
P154486
|
FINISHED |
| Object | Jews |
—
|
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: Jews | Statement: [Tomainia, hasPersecutedGroup, Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersecutedGroup Context triple: [Tomainia, hasPersecutedGroup, Jews]
-
A.
hasCrimeGroup
Indicates a relationship where an entity is associated with, belongs to, or is controlled by a particular criminal group or organization.
-
B.
hasPerpetrators
Indicates that certain entities are responsible for carrying out, committing, or executing a particular act, event, or wrongdoing.
-
C.
accusedGroup
Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
-
D.
wasPersecutedBy
Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
-
E.
consideredCriminalBy
Indicates that one party regards or classifies another party as a criminal according to its own laws, rules, or judgments.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d558748190a51b5732a3e6713c |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:21 p.m.