Triple
T9946851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Sheldon |
E195224
|
entity |
| Predicate | forcedToWrite |
P4672
|
FINISHED |
| Object | new Misery Chastain novel |
—
|
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: new Misery Chastain novel | Statement: [Paul Sheldon, forcedToWrite, new Misery Chastain novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forcedToWrite Context triple: [Paul Sheldon, forcedToWrite, new Misery Chastain novel]
-
A.
forcedBy
chosen
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
B.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
C.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
-
D.
likelyWrittenFrom
Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
-
E.
forcedToReturnTo
Indicates that one entity is compelled, against its preference or by external pressure or requirement, to go back to a previous place, state, or situation.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb657b35c81909448e93999f6e77c |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.