Triple
T33318986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Litigation Group |
E853088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal advocacy organization division |
C32381
|
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: legal advocacy organization division Context triple: [Litigation Group, instanceOf, legal advocacy organization division]
-
A.
legal services organization
A legal services organization is an entity that provides legal advice, representation, and related support—often focusing on underserved or specific client groups—through licensed attorneys and legal professionals.
-
B.
legal services organization
A legal services organization is an entity that provides legal advice, representation, and related support—often focusing on specific client groups or issues—to help individuals or organizations navigate and resolve legal matters.
-
C.
legal service branch
chosen
A legal service branch is an organizational unit within a larger entity that provides specialized legal advice, representation, and support to ensure compliance with laws and regulations.
-
D.
human rights organization division
A human rights organization division is a specialized internal unit responsible for planning, coordinating, and executing activities related to the protection, promotion, and advocacy of specific human rights issues within the broader organization.
-
E.
legal organization collective
A legal organization collective is a formally recognized group of individuals or entities that operates under a shared legal structure to pursue common organizational goals, rights, and responsibilities.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.