Triple

T24863042
Position Surface form Disambiguated ID Type / Status
Subject CPN E622203 entity
Predicate legalStatusDuringWWII P19660 FINISHED
Object banned by German occupation authorities 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: banned by German occupation authorities | Statement: [CPN, legalStatusDuringWWII, banned by German occupation authorities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: legalStatusDuringWWII
Context triple: [CPN, legalStatusDuringWWII, banned by German occupation authorities]
  • A. legalStatusDuringWWI
    Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
  • B. statusDuringWorldWarII chosen
    Indicates the role, condition, or classification an entity had specifically during the period of World War II.
  • C. sideInWorldWarII
    Indicates that an entity was aligned with or participated on a particular side during World War II.
  • D. operatorDuringWorldWarII
    Indicates that an entity operated or was active in its role during the period of World War II.
  • E. ownerDuringWorldWarII
    Indicates that one entity was the owner of another entity specifically during the time period of World War II.
  • 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_69e2fac350d08190b3affde1b451a8c5 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f6135293908190809e255bf6334760 completed May 2, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69f611a72780819082f44e66ca2c6ac9 completed May 2, 2026, 3 p.m.
Created at: April 18, 2026, 5:22 a.m.