Triple
T11171876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Keene |
E264291
|
entity |
| Predicate | dealPurpose |
P79
|
FINISHED |
| Object | to reduce his prison sentence |
—
|
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: to reduce his prison sentence | Statement: [James Keene, dealPurpose, to reduce his prison sentence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dealPurpose Context triple: [James Keene, dealPurpose, to reduce his prison sentence]
-
A.
typicalLoanPurpose
Indicates the usual or intended purpose for which a loan is taken or used.
-
B.
orderPurpose
Indicates that an order is placed with the specific purpose or intended use of the ordered item or service.
-
C.
additionalFundingPurpose
Indicates the specific reason or intended use for which additional funding is sought or allocated beyond the original amount.
-
D.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
-
E.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e89660208190b1d9e91529f5d246 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.