Triple
T7492341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1913 Kingsbury Commitment |
E177034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory settlement |
C3029
|
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: regulatory settlement Context triple: [1913 Kingsbury Commitment, instanceOf, regulatory settlement]
-
A.
legal settlement
A legal settlement is an agreement between disputing parties to resolve a legal claim or lawsuit, typically involving negotiated terms such as payment or actions, without proceeding to a final court judgment.
-
B.
settlement policy
Settlement policy is a set of principles and rules that govern how disputes are resolved and agreements are reached, typically outlining procedures, criteria, and terms for negotiating and finalizing settlements.
-
C.
multistate settlement agreement
chosen
A multistate settlement agreement is a coordinated legal resolution in which multiple state authorities jointly negotiate and finalize terms with one or more parties to resolve common claims or regulatory issues across their jurisdictions.
-
D.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
E.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:43 p.m.