Triple
T27031818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legal Aid Society (New York City) |
E680937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonprofit legal services organization |
C8536
|
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: nonprofit legal services organization Context triple: [Legal Aid Society (New York City), instanceOf, nonprofit legal services organization]
-
A.
legal services organization
chosen
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.
nonprofit organization
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
D.
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.
-
E.
legal service branch
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.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:14 a.m.