Triple
T22026246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian bar associations |
E543969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal profession organization |
C41020
|
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 profession organization Context triple: [Prussian bar associations, instanceOf, legal profession organization]
-
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 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.
-
D.
legal services regulator
A legal services regulator is an authority responsible for overseeing, licensing, and enforcing standards of conduct and competence among legal service providers to protect the public interest and maintain confidence in the legal system.
-
E.
lawyers’ community
chosen
A lawyers’ community is a network of legal professionals who connect to share knowledge, collaborate on cases, support each other’s professional development, and advance common legal and ethical interests.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:24 p.m.