Triple

T19597990
Position Surface form Disambiguated ID Type / Status
Subject Delhi High Court E470396 entity
Predicate hasPowerToReview P24554 FINISHED
Object Decisions of subordinate courts in Delhi 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: Decisions of subordinate courts in Delhi | Statement: [Delhi High Court, hasPowerToReview, Decisions of subordinate courts in Delhi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPowerToReview
Context triple: [Delhi High Court, hasPowerToReview, Decisions of subordinate courts in Delhi]
  • A. canReview
    Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
  • B. hasApprovalAuthority chosen
    Indicates that an entity possesses the power or right to review and formally approve or reject decisions, actions, or requests made by others.
  • C. hasRightsOver
    Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
  • D. reviewableBy
    Indicates that an entity is subject to evaluation, inspection, or assessment by a specified agent or party.
  • E. hasDecisionMakingPower
    Indicates that one entity possesses the authority or ability to make decisions that affect another entity or a given context.
  • 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.