Triple

T494046
Position Surface form Disambiguated ID Type / Status
Subject First Petty Bench E10250 entity
Predicate sizeRelativeToCourt P14170 FINISHED
Object smaller panel compared to the Grand Bench 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: smaller panel compared to the Grand Bench | Statement: [First Petty Bench, sizeRelativeToCourt, smaller panel compared to the Grand Bench]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sizeRelativeToCourt
Context triple: [First Petty Bench, sizeRelativeToCourt, smaller panel compared to the Grand Bench]
  • A. usedCourt
    Indicates that an entity made use of or participated in legal proceedings within a particular court.
  • B. termOfCourt
    Indicates the specific judicial session or period during which a court is formally in operation for a case or legal matter.
  • C. limitedByCourtCase
    Indicates that one entity’s scope, effect, or applicability is restricted or constrained as a result of a specific court case or legal proceeding.
  • D. highCourtBench
    Indicates that a particular bench or panel of judges belongs to, or is constituted within, a high court.
  • E. hasTypeOfCourt
    Indicates that an entity is associated with or classified by a specific type or category of court.
  • 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_69a2e847df8481909239ec08ccf1e376 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f0fbfa408190aeb3b93996a35c00 completed Feb. 28, 2026, 1:43 p.m.
PD Predicate disambiguation batch_69a2edf90ca88190b6a182e5b6733612 completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eebb2c908190960a4d0c014304cd completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.