Triple
T836811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Corsair |
E18085
|
entity |
| Predicate | hasLiteraryCharacterType |
P15535
|
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: [The Corsair, hasLiteraryCharacterType, Byronic hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiteraryCharacterType Context triple: [The Corsair, hasLiteraryCharacterType, Byronic hero]
-
A.
literaryRole
chosen
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
B.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
C.
hasLiteraryForm
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
-
D.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
E.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abcf69888190b342363978273ae2 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.