Triple
T383466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothic literature |
E8728
|
entity |
| Predicate | hasTypicalPlotElement |
P5084
|
FINISHED |
| Object | family curse |
—
|
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: family curse | Statement: [Gothic literature, hasTypicalPlotElement, family curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalPlotElement Context triple: [Gothic literature, hasTypicalPlotElement, family curse]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
C.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
D.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec40ff8c81909306eb2dfe1512af |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.