Triple
T36407108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Modern Prometheus |
E896775
|
entity |
| Predicate | usedInFullTitle |
P32965
|
FINISHED |
| Object | Frankenstein; or, The Modern Prometheus |
—
|
NE NERFINISHED |
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: Frankenstein; or, The Modern Prometheus | Statement: [The Modern Prometheus, usedInFullTitle, Frankenstein; or, The Modern Prometheus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFullTitle Context triple: [The Modern Prometheus, usedInFullTitle, Frankenstein; or, The Modern Prometheus]
-
A.
usedAsTitleInFull
Indicates that something functions as a formal title within the complete, official version of a name or designation.
-
B.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
C.
usedInFullNameOf
chosen
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
D.
usedAsTitleOn
Indicates that something functions as a title applied to or displayed on a particular entity.
-
E.
usedAsTitleFrom
Indicates that something functions as a title derived from or originating from another source or context.
- 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_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:10 p.m.