Triple
T18101119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad |
E433217
|
entity |
| Predicate | hasLiteraryArchetype |
P102015
|
FINISHED |
| Object | Byronic 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: Byronic hero | Statement: [Conrad, hasLiteraryArchetype, Byronic hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiteraryArchetype Context triple: [Conrad, hasLiteraryArchetype, Byronic hero]
-
A.
usesCharacterArchetype
chosen
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
B.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
C.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
D.
hasLiteraryConnection
Indicates a relationship in which one entity is connected to another through a literary link, such as authorship, reference, influence, adaptation, or shared appearance in written works.
-
E.
nameInLiterature
Indicates that a particular name is used or appears for an entity within a literary work 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddb5e6208190b3c3cce3b95d66ad |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.