Triple
T6393683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | post‑1987 Rule 35 |
E143888
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | current framework of Rule 35 |
C6256
|
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: current framework of Rule 35 Context triple: [post‑1987 Rule 35, instanceOf, current framework of Rule 35]
-
A.
judicial rules
Judicial rules are formal guidelines and procedures established by courts to govern how legal cases are processed, decided, and managed within the judicial system.
-
B.
regulatory framework
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
C.
treaty implementation rules
Treaty implementation rules are the detailed legal and administrative provisions that translate a treaty’s general obligations into specific, enforceable procedures and standards within a jurisdiction.
-
D.
formal rules
Formal rules are explicitly defined, codified guidelines or principles that govern behavior, procedures, or decision-making within a specific system or organization.
-
E.
rules of procedure
chosen
Rules of procedure are formal guidelines that govern how decisions are proposed, discussed, and made within an organization, assembly, or legal process.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:34 p.m.