Triple
T29050519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necroswords |
E735251
|
entity |
| Predicate | canBeSummonedFrom |
P119734
|
FINISHED |
| Object | Hela's body |
—
|
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: Hela's body | Statement: [Necroswords, canBeSummonedFrom, Hela's body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSummonedFrom Context triple: [Necroswords, canBeSummonedFrom, Hela's body]
-
A.
canBeSummonedByPlayer
Indicates that the entity is capable of being brought into the game world or into action through a summoning action performed by a player.
-
B.
canSummonToken
Indicates that an entity has the ability to create or bring forth a specific token into play or existence.
-
C.
summonedIn
chosen
Indicates that one entity is called forth, invoked, or brought into presence within the context, location, or event represented by another entity.
-
D.
summonedMinionText
Indicates that one entity has called forth or created another entity to serve as its minion.
-
E.
summonedMinionType
Indicates that one entity has summoned or created another entity specifically as a minion of a given type.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 28, 2026, 10:08 a.m.