Triple
T15664675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAPD consent decree (2001–2013) |
E377156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal court consent decree |
C2080
|
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: federal court consent decree Context triple: [LAPD consent decree (2001–2013), instanceOf, federal court consent decree]
-
A.
multistate settlement agreement
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.
-
B.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
C.
legal decree
chosen
A legal decree is an authoritative, formal order issued by a governmental or judicial body that has the force of law and mandates specific actions, rights, or obligations.
-
D.
federal facility compliance agreement
A federal facility compliance agreement is a formal, legally binding document between a federal agency and a regulatory authority that outlines specific actions, schedules, and conditions required for the facility to achieve and maintain compliance with applicable environmental or safety laws and regulations.
-
E.
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.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:16 a.m.