Triple
T9607225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavia & Harcourt |
E232001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal services provider |
C9774
|
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 services provider Context triple: [Pavia & Harcourt, instanceOf, legal services provider]
-
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
chosen
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
A legal service is a professional offering that provides clients with advice, representation, and assistance in understanding and resolving matters governed by law.
-
D.
public service advocate
A public service advocate is an individual who actively promotes, defends, and advances the interests of the public by influencing policies, raising awareness, and ensuring government and institutions are accountable and responsive to community needs.
-
E.
commercial legal research platform
A commercial legal research platform is a subscription-based digital service that provides lawyers and legal professionals with searchable access to case law, statutes, regulations, secondary sources, and analytical tools to support legal analysis and decision-making.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:08 p.m.