Triple
T25651997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee Drug Courts |
E643125
|
entity |
| Predicate | outcomeMeasure |
P35854
|
FINISHED |
| Object | reduced re-arrest rates |
—
|
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: reduced re-arrest rates | Statement: [Tennessee Drug Courts, outcomeMeasure, reduced re-arrest rates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeMeasure Context triple: [Tennessee Drug Courts, outcomeMeasure, reduced re-arrest rates]
-
A.
outcomeSummary
Indicates a concise description or overview of the result or consequences of an action, event, or process.
-
B.
successMetric
chosen
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
C.
enabledMeasurementOf
Indicates that one entity made it possible or allowed another entity to perform or obtain a specific measurement.
-
D.
aimsToMeasure
Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
-
E.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa88aec819082bca8efba424a91 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 6:26 p.m.