Triple
T26082376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice Fellowship |
E657879
|
entity |
| Predicate | supportsReformType |
P194061
|
FINISHED |
| Object | sentencing reform |
—
|
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: sentencing reform | Statement: [Justice Fellowship, supportsReformType, sentencing reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReformType Context triple: [Justice Fellowship, supportsReformType, sentencing reform]
-
A.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
B.
canReform
Indicates that an entity has the ability or potential to change, improve, or be corrected from a previous state, behavior, or condition.
-
C.
supportsForms
Indicates that one entity is capable of handling, accepting, or working with specific forms or form types associated with another entity.
-
D.
reformedWithSupportFrom
Indicates that an entity underwent reform or significant change with the assistance, backing, or encouragement of another entity.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: April 26, 2026, 7:39 p.m.