Triple
T3969028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Adult Probation Department |
E92283
|
entity |
| Predicate | hasClientGroup |
P53231
|
FINISHED |
| Object | justice-involved adults |
—
|
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: justice-involved adults | Statement: [San Francisco Adult Probation Department, hasClientGroup, justice-involved adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClientGroup Context triple: [San Francisco Adult Probation Department, hasClientGroup, justice-involved adults]
-
A.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
B.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
C.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
D.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
E.
hasKeyGroup
Indicates that an entity is associated with a particular key group that governs or organizes its access, classification, or control.
- F. None of above. chosen
Provenance (4 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefac8f7a48190b065487ce090eaf2 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:32 p.m.