Triple

T166884
Position Surface form Disambiguated ID Type / Status
Subject Ministries Trial E3034 entity
Predicate triedRole P5673 FINISHED
Object high-ranking officials of the Reich government 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: high-ranking officials of the Reich government | Statement: [Ministries Trial, triedRole, high-ranking officials of the Reich government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: triedRole
Context triple: [Ministries Trial, triedRole, high-ranking officials of the Reich government]
  • A. refersToRole
    Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
  • B. deFactoRole
    Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
  • C. role
    Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
  • D. hasRole
    Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
  • E. playedKeyRoleIn
    Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
  • 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_69a2524ce1e48190ab066bf72859f474 completed Feb. 28, 2026, 2:26 a.m.
NER Named-entity recognition batch_69a25884c8d88190bc4cb4e3541e8116 completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a25664ba8081908ac298511a9fc5ba completed Feb. 28, 2026, 2:43 a.m.
PDg Predicate description generation batch_69a256eb46ec81909c730000e5041d0d completed Feb. 28, 2026, 2:46 a.m.
Created at: Feb. 28, 2026, 2:34 a.m.