Triple

T9324916
Position Surface form Disambiguated ID Type / Status
Subject High Council of the Judiciary E224361 entity
Predicate disciplinaryPowerOver P6502 FINISHED
Object ordinary judges 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: ordinary judges | Statement: [High Council of the Judiciary, disciplinaryPowerOver, ordinary judges]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: disciplinaryPowerOver
Context triple: [High Council of the Judiciary, disciplinaryPowerOver, ordinary judges]
  • A. involvedPower
    Indicates that a particular power, authority, or state is a participant or actor in the referenced event, situation, or relationship.
  • B. exclusivePower
    Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
  • C. powerBy
    Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
  • D. exercisedPowerOver chosen
    Indicates that one entity exerted control, influence, or authority over another entity.
  • E. powers
    Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
  • 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_69ca8426d48481909596360f7791c7dd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd36f77c808190aa5489c4305fd67d completed April 1, 2026, 3:17 p.m.
PD Predicate disambiguation batch_69cc7a643924819097f01144734901cf completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:38 p.m.