Triple

T35128735
Position Surface form Disambiguated ID Type / Status
Subject Rule 12 – Bill of Particulars E1014380 entity
Predicate remedyForm P13744 FINISHED
Object motion for bill of particulars 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: motion for bill of particulars | Statement: [Rule 12 – Bill of Particulars, remedyForm, motion for bill of particulars]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: remedyForm
Context triple: [Rule 12 – Bill of Particulars, remedyForm, motion for bill of particulars]
  • A. remedy
    Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
  • B. remedySought
    Indicates that a particular legal or corrective action is being requested as a solution or relief in response to a problem or dispute.
  • C. remainsForm
    Indicates that one entity is the physical remains or residual form resulting from the transformation, decay, or destruction of another entity.
  • D. typeOfRemedy chosen
    Indicates that one entity is a specific kind or category of remedy in relation to another entity.
  • E. hasRemedy
    Indicates that one entity serves as a remedy, treatment, or corrective measure for a problem, condition, or undesirable state associated with 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_69f76dd8b6948190aaa32b081816bd94 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78ce78b508190955848e133398dc8 completed May 3, 2026, 5:59 p.m.
PD Predicate disambiguation batch_69f78b8f4cc08190b49fccd798cb25d7 completed May 3, 2026, 5:53 p.m.
Created at: May 3, 2026, 4:02 p.m.