Triple
T2912786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Small and Disadvantaged Business Utilization |
E63722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | small business advocacy office |
C5922
|
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: small business advocacy office Context triple: [Office of Small and Disadvantaged Business Utilization, instanceOf, small business advocacy office]
-
A.
advocacy unit
chosen
An advocacy unit is an organized group or department dedicated to influencing policies, decisions, or public opinion in support of specific causes or interests.
-
B.
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.
-
C.
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.
-
D.
government liaison office
A government liaison office is an organizational unit that facilitates communication, coordination, and collaboration between a government entity and external stakeholders such as other agencies, businesses, or the public.
-
E.
business directory service
A business directory service is a platform that collects, organizes, and presents structured information about businesses to help users discover, compare, and contact relevant providers.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:11 p.m.