Triple
T35129534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 34 – Judgment on the Pleadings |
E1014399
|
entity |
| Predicate | mayBeInvokedBy |
P59606
|
FINISHED |
| Object | motion of a party |
—
|
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 of a party | Statement: [Rule 34 – Judgment on the Pleadings, mayBeInvokedBy, motion of a party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeInvokedBy Context triple: [Rule 34 – Judgment on the Pleadings, mayBeInvokedBy, motion of a party]
-
A.
canBeInvokedBy
chosen
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
B.
canBeInvokedFrom
Indicates that one entity (such as a function, method, or component) is able to be called or triggered directly from another specified context or entity.
-
C.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
-
D.
isUsedToInvoke
Indicates that one entity serves as a means or mechanism to trigger, call, or activate another entity or process.
-
E.
kannAbberufenWerdenVon
Indicates that an entity can be dismissed or removed from its position by 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_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.