Triple
T11659526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totem of Undying |
E277086
|
entity |
| Predicate | canBeUsedAgainst |
P13821
|
FINISHED |
| Object | void damage |
—
|
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: void damage | Statement: [Totem of Undying, canBeUsedAgainst, void damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedAgainst Context triple: [Totem of Undying, canBeUsedAgainst, void damage]
-
A.
usedAgainst
chosen
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
B.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
C.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
effectivenessAgainst
Indicates how well one entity performs in countering, influencing, or mitigating the impact of another entity.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.