Triple

T35129470
Position Surface form Disambiguated ID Type / Status
Subject Rule 33 – Demurrer to Evidence E1014398 entity
Predicate partyWhoMayFile P8472 FINISHED
Object defendant 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: defendant | Statement: [Rule 33 – Demurrer to Evidence, partyWhoMayFile, defendant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: partyWhoMayFile
Context triple: [Rule 33 – Demurrer to Evidence, partyWhoMayFile, defendant]
  • A. permitsFilingIn
    Indicates that one entity authorizes or allows another entity to submit or initiate a filing within its jurisdiction, system, or process.
  • B. legalParties
    Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
  • C. partiesAre
    Indicates that certain entities are the participants or sides involved in a particular relationship, agreement, or event.
  • D. eligibleParties chosen
    Indicates that certain entities are qualified or permitted to participate in, benefit from, or be subject to a specified agreement, process, or condition.
  • E. filedWith
    Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
  • 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.