Triple
T15127093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlakviða |
E361317
|
entity |
| Predicate | characterRoleOfGunnar |
P115276
|
FINISHED |
| Object | tragic 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: tragic hero | Statement: [Atlakviða, characterRoleOfGunnar, tragic hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleOfGunnar Context triple: [Atlakviða, characterRoleOfGunnar, tragic hero]
-
A.
characterRoleOfGriffin
Indicates that an entity has the character role of a griffin within a given context, such as a story, game, or artwork.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
characterInWorkDescribedAs
chosen
Indicates that a character is portrayed or described in a particular way within a specific work.
-
D.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another entity.
-
E.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a1b9288190954f2d92549805e5 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.