Triple
T19102685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras Bar |
E467574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal professional association |
C7
|
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 professional association Context triple: [Madras Bar, instanceOf, legal professional association]
-
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.
professional association
chosen
A professional association is an organized group of individuals in the same occupation or field that advances shared professional interests through networking, standards, advocacy, and continuing education.
-
E.
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.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.