Triple
T36407118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Modern Prometheus |
E896775
|
entity |
| Predicate | usedInAcademicDiscourse |
P6966
|
FINISHED |
| Object | literary criticism of Frankenstein |
—
|
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: literary criticism of Frankenstein | Statement: [The Modern Prometheus, usedInAcademicDiscourse, literary criticism of Frankenstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAcademicDiscourse Context triple: [The Modern Prometheus, usedInAcademicDiscourse, literary criticism of Frankenstein]
-
A.
academicUse
Indicates that something is intended for, suitable for, or used within an academic or educational context.
-
B.
scholarlyUse
chosen
Indicates that something is used for academic, educational, or research-related purposes.
-
C.
hasAcademicDiscussion
Indicates that an academic or scholarly discussion, debate, or exchange of ideas occurs between the related entities.
-
D.
usedInBibliographies
Indicates that something is cited or listed as a reference within bibliographies.
-
E.
usedInPoliticalDiscourse
Indicates that something is employed as a term, concept, or reference within political discussion, debate, or rhetoric.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:10 p.m.