Triple
T29913057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Public Defense (Washington) |
E759720
|
entity |
| Predicate | servesClientGroup |
P93846
|
FINISHED |
| Object | indigent persons |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: indigent persons | Statement: [Office of Public Defense (Washington), servesClientGroup, indigent persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesClientGroup Context triple: [Office of Public Defense (Washington), servesClientGroup, indigent persons]
-
A.
servesClientsIn
Indicates that an entity provides services to clients located within a specified geographic area or jurisdiction.
-
B.
hasClientGroup
Indicates that an entity is associated with, or belongs to, a particular group of clients.
-
C.
servesGroup
chosen
Indicates that one entity provides services or functions in support of a particular group or collective.
-
D.
primaryClientGroup
Indicates the main group of clients that an entity primarily serves or is chiefly associated with.
-
E.
servedNativeGroup
Indicates that one entity provided service, assistance, or work to a particular native or indigenous group.
- F. None of above.
Provenance (3 batches)
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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 29, 2026, 6:11 p.m.