Triple
T33827873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blade Artist |
E867006
|
entity |
| Predicate | protagonistNewLifeLocation |
P81317
|
FINISHED |
| Object | abroad |
—
|
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: abroad | Statement: [The Blade Artist, protagonistNewLifeLocation, abroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistNewLifeLocation Context triple: [The Blade Artist, protagonistNewLifeLocation, abroad]
-
A.
protagonistLocation
Indicates the location or setting where the story’s main protagonist is situated at a given time.
-
B.
mainCharacterStartsNewLifeIn
chosen
Indicates that the story’s main character begins a significantly different or renewed phase of life in the specified place or context.
-
C.
protagonistHomeworld
Indicates the homeworld or place of origin associated with a story’s main protagonist.
-
D.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
E.
protagonistEmployerLocation
Indicates the location where the protagonist’s employer is based or operates.
- 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_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:46 a.m.