Triple
T8156938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heathcliff |
E190472
|
entity |
| Predicate | inspiredArchetype |
P57243
|
FINISHED |
| Object | dark romantic hero |
—
|
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: dark romantic hero | Statement: [Heathcliff, inspiredArchetype, dark romantic hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredArchetype Context triple: [Heathcliff, inspiredArchetype, dark romantic hero]
-
A.
inspiredTrope
chosen
Indicates that one trope serves as the creative or conceptual inspiration for another trope.
-
B.
inspiredArtist
Indicates that one artist has served as a source of creative influence or inspiration for another artist.
-
C.
inspiredAuthor
Indicates that one entity served as a source of creative or intellectual inspiration for an author entity.
-
D.
inspiredField
Indicates that one entity served as a source of inspiration or influence for the development, direction, or characteristics of a particular field or domain.
-
E.
visionaryOf
Indicates that one entity is the original conceiver or driving visionary behind the creation, direction, or concept of another 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d8a37481909397b5cc321b94be |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.