Triple
T11658992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zombie (Minecraft) |
E277075
|
entity |
| Predicate | takesExtraDamageFrom |
P88334
|
FINISHED |
| Object | Smite-enchanted weapons |
—
|
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: Smite-enchanted weapons | Statement: [Zombie (Minecraft), takesExtraDamageFrom, Smite-enchanted weapons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesExtraDamageFrom Context triple: [Zombie (Minecraft), takesExtraDamageFrom, Smite-enchanted weapons]
-
A.
cannotBeDamagedBy
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
-
B.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
C.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
-
D.
tookHeavyDamageAt
Indicates that an entity experienced severe or substantial damage at a specific location or point in time.
-
E.
damageBasis
chosen
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
- 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.