Triple
T35129483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 33 – Demurrer to Evidence |
E1014398
|
entity |
| Predicate | filedAs |
P182310
|
FINISHED |
| Object | motion |
—
|
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 | Statement: [Rule 33 – Demurrer to Evidence, filedAs, motion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filedAs Context triple: [Rule 33 – Demurrer to Evidence, filedAs, motion]
-
A.
filedWith
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
-
B.
placeOfFiling
Indicates the location or jurisdiction where a legal document, case, or claim is formally submitted or recorded.
-
C.
filingTypeCode
Indicates the specific category or type of filing associated with a submitted document or record.
-
D.
filingStage
Indicates the procedural phase or step that a filing or submission is currently in within a formal process or workflow.
-
E.
legalActionFiled
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or 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_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_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c337cec8190bfdab225a3cc96db |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4:02 p.m.