Triple
T241528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Settlement Agreement |
E4941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multistate settlement agreement |
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: multistate settlement agreement Context triple: [Master Settlement Agreement, instanceOf, multistate settlement agreement]
-
A.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
B.
bi-state agency
A bi-state agency is a governmental or quasi-governmental organization jointly created and governed by two neighboring states to manage shared resources, infrastructure, or regulatory responsibilities across their common jurisdiction.
-
C.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
D.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
E.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
- F. None of above. chosen
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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.