Triple
T35129569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 35 – Summary Judgments |
E1014400
|
entity |
| Predicate | motionFiledBy |
P178453
|
FINISHED |
| Object | claimant |
—
|
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: claimant | Statement: [Rule 35 – Summary Judgments, motionFiledBy, claimant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motionFiledBy Context triple: [Rule 35 – Summary Judgments, motionFiledBy, claimant]
-
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.
legalActionFiled
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or court.
-
C.
petitionFiledBy
chosen
Indicates that a formal petition has been submitted or initiated by a particular party or entity.
-
D.
placeOfFiling
Indicates the location or jurisdiction where a legal document, case, or claim is formally submitted or recorded.
-
E.
mayFile
Indicates that an entity is permitted or authorized to submit or register a formal document or application.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c66345081909bed56b0b3686432 |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.