Triple

T19597991
Position Surface form Disambiguated ID Type / Status
Subject Delhi High Court E470396 entity
Predicate hasPowerToPunishFor P101197 FINISHED
Object Contempt of court 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: Contempt of court | Statement: [Delhi High Court, hasPowerToPunishFor, Contempt of court]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPowerToPunishFor
Context triple: [Delhi High Court, hasPowerToPunishFor, Contempt of court]
  • A. authorizesPunishment chosen
    Indicates that one entity grants permission or legal authority for another entity to impose a punishment.
  • B. hasPunishment
    Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
  • C. exercisedPowerOver
    Indicates that one entity exerted control, influence, or authority over another entity.
  • D. exercisedPowerWith
    Indicates that one entity actively used or exerted power in conjunction with another entity, implying a shared or coordinated exercise of authority or influence.
  • E. hasCriminalJurisdictionOver
    Indicates that one authority or legal body holds the power to investigate, prosecute, and adjudicate criminal offenses committed within a specified scope or territory in relation to another entity.
  • 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_69d8e510024481908415c0d616fa6186 completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e6407c52c081908704d3a4dd6e853b completed April 20, 2026, 3:04 p.m.
PD Predicate disambiguation batch_69e514e166dc8190a0f147e0b4c8bbe7 completed April 19, 2026, 5:46 p.m.
Created at: April 10, 2026, 1:43 p.m.