Triple
T28219058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Decay of the Angel |
E711398
|
entity |
| Predicate | concludesCharacterArcOf |
P88460
|
FINISHED |
| Object | Shigekuni Honda |
—
|
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: Shigekuni Honda | Statement: [The Decay of the Angel, concludesCharacterArcOf, Shigekuni Honda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludesCharacterArcOf Context triple: [The Decay of the Angel, concludesCharacterArcOf, Shigekuni Honda]
-
A.
characterArcOutcome
Indicates the resulting change, resolution, or final state of a character’s personal journey or development over the course of a narrative.
-
B.
concludesStoryOf
chosen
Indicates that one entity brings the narrative or storyline of another entity to an end.
-
C.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
D.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
E.
linkedCharacterArc
Indicates that one character’s narrative development is directly connected to, influenced by, or dependent on another character’s arc.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434f9f888190bd43fde92cd729fe |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:45 p.m.