Triple
T13490659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WTO dispute settlement |
E318623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rules-based system |
C4383
|
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: rules-based system Context triple: [WTO dispute settlement, instanceOf, rules-based system]
-
A.
policy rule
A policy rule is a formal, enforceable statement that defines specific conditions and corresponding actions or constraints to guide decision-making and behavior within a system or organization.
-
B.
subrule
A subrule is a subordinate rule that refines, constrains, or specifies the conditions and behavior of a broader parent rule within a rule-based system.
-
C.
formal rules
chosen
Formal rules are explicitly defined, codified guidelines or principles that govern behavior, procedures, or decision-making within a specific system or organization.
-
D.
joint planning and execution system
A joint planning and execution system is an integrated framework that enables multiple agents or stakeholders to collaboratively create, coordinate, and carry out shared plans toward common goals in dynamic environments.
-
E.
directive-based programming model
A directive-based programming model is a high-level parallel programming approach where developers annotate code with compiler-interpreted directives (pragmas) to express parallelism and data movement without explicitly managing low-level threading or synchronization details.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:43 p.m.