Triple
T28566051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kill Ari (Part I) |
E722679
|
entity |
| Predicate | isPartOfStoryArc |
P38554
|
FINISHED |
| Object | Ari Haswari arc |
—
|
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: Ari Haswari arc | Statement: [Kill Ari (Part I), isPartOfStoryArc, Ari Haswari arc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfStoryArc Context triple: [Kill Ari (Part I), isPartOfStoryArc, Ari Haswari arc]
-
A.
isSideStoryTo
Indicates that one narrative work is a supplementary or tangential story that expands on, but is not central to, the main storyline of another work.
-
B.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
C.
hasPartInNarrative
chosen
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
D.
storyArcStart
Indicates the point in a narrative where a particular story arc or plotline begins.
-
E.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 28, 2026, 4:07 a.m.