Triple
T19268426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Seward |
E481850
|
entity |
| Predicate | initiallyExplainsRenfield |
P135370
|
FINISHED |
| Object | through psychiatry |
—
|
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: through psychiatry | Statement: [Jack Seward, initiallyExplainsRenfield, through psychiatry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyExplainsRenfield Context triple: [Jack Seward, initiallyExplainsRenfield, through psychiatry]
-
A.
roleInVolturi
Indicates that one entity holds a specific position, function, or membership role within the Volturi group or organization in relation to another entity.
-
B.
vampireType
Indicates that one entity is classified as a specific type or category of vampire in relation to another entity.
-
C.
fullyIntroducedAsAntagonistIn
Indicates that an entity is completely and explicitly presented in a work as an antagonist within the specified context or narrative.
-
D.
turnedIntoVampireIn
Indicates that an entity became a vampire at or within a specified place or context.
-
E.
focusesOnVillain
Indicates that the primary attention, narrative emphasis, or activity is directed toward a villain as the central subject.
- F. None of above. chosen
Provenance (4 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbb68d0c819083ba0ce680dd7d99 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:29 p.m.