Triple
T20684482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capaneus |
E508377
|
entity |
| Predicate | literaryArchetypeOf |
P60013
|
FINISHED |
| Object | blasphemous warrior |
—
|
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: blasphemous warrior | Statement: [Capaneus, literaryArchetypeOf, blasphemous warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryArchetypeOf Context triple: [Capaneus, literaryArchetypeOf, blasphemous warrior]
-
A.
usesCharacterArchetype
Indicates that one entity employs or incorporates the character archetype represented by another entity in its narrative or design.
-
B.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
-
C.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
D.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
E.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6beaae5608190ac8cc64aa4717d53 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.