Triple
T26897165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal winter |
E677925
|
entity |
| Predicate | resolvedByCharacter |
P161981
|
FINISHED |
| Object | Anna |
—
|
NE NERFINISHED |
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: Anna | Statement: [Eternal winter, resolvedByCharacter, Anna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolvedByCharacter Context triple: [Eternal winter, resolvedByCharacter, Anna]
-
A.
explainedByCharacter
Indicates that something (such as an event, situation, or piece of information) is explained or clarified by a particular character.
-
B.
resolvedIn
Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
-
C.
characterResolution
Indicates the process or outcome by which a character’s conflicts, arcs, or internal struggles are brought to a conclusion or clarified within a narrative.
-
D.
dismissesCharacter
Indicates that one character rejects, disbelieves, or disregards another character, often minimizing their importance, ideas, or concerns.
-
E.
allyOfCharacter
Indicates that one character maintains an alliance or supportive partnership with another character.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:48 a.m.