Triple
T10339740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randle Patrick McMurphy |
E243097
|
entity |
| Predicate | reasonForCommitment |
P24494
|
FINISHED |
| Object | pleads insanity to avoid prison labor |
—
|
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: pleads insanity to avoid prison labor | Statement: [Randle Patrick McMurphy, reasonForCommitment, pleads insanity to avoid prison labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCommitment Context triple: [Randle Patrick McMurphy, reasonForCommitment, pleads insanity to avoid prison labor]
-
A.
reasonForPledge
Indicates the motivation or justification behind making a particular pledge or commitment.
-
B.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
C.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
D.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
-
E.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:54 a.m.