Triple
T25686670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order VI (Pleadings generally) |
E644083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | order under the Code of Civil Procedure, 1908 |
C3358
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: order under the Code of Civil Procedure, 1908 Context triple: [Order VI (Pleadings generally), instanceOf, order under the Code of Civil Procedure, 1908]
-
A.
source of civil procedural law
A source of civil procedural law is any formally recognized authority—such as constitutions, statutes, court rules, judicial precedents, and international treaties—that establishes or influences the rules governing the conduct of civil litigation.
-
B.
procedural law
chosen
Procedural law is the body of legal rules that governs the processes and methods by which courts and other legal authorities enforce rights, obligations, and justice in practice.
-
C.
order division
An order division represents the partitioning of a customer’s order into smaller, manageable segments (such as by shipment, fulfillment location, or processing stage) for operational handling and tracking.
-
D.
bench of the Bombay High Court
A bench of the Bombay High Court is a panel of one or more judges of the court constituted to hear and decide specific cases or categories of matters within its jurisdiction.
-
E.
contingency order
A contingency order is a type of trading instruction that becomes active or executable only when specified conditions or events occur, such as the execution of another order or the market reaching a certain price.
- F. None of above.
Provenance (1 batch)
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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:09 p.m.