Triple
T3773831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraft Center for Community Health |
E83258
|
entity |
| Predicate | targetIssue |
P11722
|
FINISHED |
| Object | barriers to accessing healthcare |
—
|
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: barriers to accessing healthcare | Statement: [Kraft Center for Community Health, targetIssue, barriers to accessing healthcare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetIssue Context triple: [Kraft Center for Community Health, targetIssue, barriers to accessing healthcare]
-
A.
hasTargetIssue
chosen
Indicates that an entity is associated with or directed toward a specific issue, problem, or concern as its focus.
-
B.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
C.
knownIssue
Indicates that the subject has an issue or problem that is already identified, recognized, or documented.
-
D.
worksOnIssue
Indicates that an entity (typically a person or team) is actively engaged in addressing, resolving, or contributing work toward a specific issue.
-
E.
raisesIssue
Indicates that one entity brings up, reports, or formally submits a concern, problem, or topic for attention to another entity or system.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc594c50819099ab5ac1b82f61a6 |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.