Triple

T4402804
Position Surface form Disambiguated ID Type / Status
Subject Japanese Communist Party E93654 entity
Predicate wasPersecutedDuring P33150 FINISHED
Object prewar Japan 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: prewar Japan | Statement: [Japanese Communist Party, wasPersecutedDuring, prewar Japan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasPersecutedDuring
Context triple: [Japanese Communist Party, wasPersecutedDuring, prewar Japan]
  • A. wasPersecutedBy
    Indicates that an entity was subjected to persistent hostility, oppression, or harmful treatment carried out by another entity.
  • B. persecutedDuring
    Indicates that one entity systematically harassed, oppressed, or victimized another entity during a specified time period or event.
  • C. persecutedIn chosen
    Indicates that an entity is subjected to oppression, harassment, or unfair treatment within a particular place, context, or time period.
  • D. methodOfPersecution
    Indicates the specific means, technique, or process by which an act of persecution is carried out.
  • E. persecutionHistory
    Indicates that an entity has experienced, participated in, or is otherwise associated with acts of persecution in the past.
  • 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_69b345158c748190a2c040fce2da9980 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b352d08a0c8190ac6c125df40eca75 completed March 12, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69b34f5b36a881909bf2e970aa523390 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:28 p.m.