Triple
T29050508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necroswords |
E735251
|
entity |
| Predicate | requiresWielder |
P193936
|
FINISHED |
| Object | Hela |
—
|
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: Hela | Statement: [Necroswords, requiresWielder, Hela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresWielder Context triple: [Necroswords, requiresWielder, Hela]
-
A.
wielderRole
Indicates the specific role or function an entity has in relation to the item or power it wields.
-
B.
wieldedFrom
Indicates that an entity uses or brandishes another entity as a weapon or tool originating from a particular source or location.
-
C.
requiresAttunementOriginal
Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
-
D.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
E.
laterWielder
Indicates that one entity becomes the wielder or user of an object or power after another entity who wielded it earlier.
- F. None of above. chosen
Provenance (4 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_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 28, 2026, 10:08 a.m.