Triple
T11658966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zombie (Minecraft) |
E277075
|
entity |
| Predicate | attackDamageRange |
P47565
|
FINISHED |
| Object | 2–9 (Java Edition, depending on difficulty) |
—
|
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: 2–9 (Java Edition, depending on difficulty) | Statement: [Zombie (Minecraft), attackDamageRange, 2–9 (Java Edition, depending on difficulty)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackDamageRange Context triple: [Zombie (Minecraft), attackDamageRange, 2–9 (Java Edition, depending on difficulty)]
-
A.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
B.
frontArmorRange
Indicates the range or extent of protective armor coverage on the front-facing side of an entity.
-
C.
damageBasis
Indicates the underlying reason, cause, or basis on which damage is determined or assessed in a given context.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
attackerStrength
chosen
Indicates the level or magnitude of power, force, or capability possessed by the attacking entity in a given interaction or scenario.
- 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.