Triple
T19416140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Weak and the Wicked |
E485719
|
entity |
| Predicate | sourceWorkSubject |
P7040
|
FINISHED |
| Object | author's experiences in prison |
—
|
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: author's experiences in prison | Statement: [The Weak and the Wicked, sourceWorkSubject, author's experiences in prison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkSubject Context triple: [The Weak and the Wicked, sourceWorkSubject, author's experiences in prison]
-
A.
subjectOfWork
chosen
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
B.
subjectOfWorkBy
Indicates that one entity is the main topic or focus of a work (such as a book, article, or artwork) created by another entity.
-
C.
sourceWorkSection
Indicates that one entity is a specific section or part extracted from a larger source work.
-
D.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
sourceWorkFirstPerformed
Indicates the original performance event or context in which a work was first publicly performed.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af9c8fc81909860de10b6720207 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.