Triple
T33827871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blade Artist |
E867006
|
entity |
| Predicate | hasProtagonistPast |
P16448
|
FINISHED |
| Object | violent past |
—
|
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: violent past | Statement: [The Blade Artist, hasProtagonistPast, violent past]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistPast Context triple: [The Blade Artist, hasProtagonistPast, violent past]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasProtagonistBackground
Indicates that a work or narrative features a specified background or origin story for its main protagonist.
-
C.
hasHeirProtagonist
Indicates that an entity serves as the primary heir or central inheriting figure in relation to another entity.
-
D.
hasHumanProtagonists
Indicates that the primary characters driving the narrative are human beings rather than non-human entities.
-
E.
hasTragicPast
chosen
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a01d48f41f4819093a5b47288a073c1 |
completed | May 11, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a01d3fa278c8190838174dd96ef5dde |
completed | May 11, 2026, 1:04 p.m. |
Created at: May 1, 2026, 1:46 a.m.