Triple
T37661384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enderman |
E937724
|
entity |
| Predicate | attackDamageEasy |
P138110
|
FINISHED |
| Object | 4.5 hearts |
—
|
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: 4.5 hearts | Statement: [Enderman, attackDamageEasy, 4.5 hearts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackDamageEasy Context triple: [Enderman, attackDamageEasy, 4.5 hearts]
-
A.
attackValue
Indicates the offensive strength or damage potential an entity can inflict in an interaction or combat scenario.
-
B.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
C.
attackName
Indicates the specific name or designation given to an attack action or offensive maneuver.
-
D.
hasBaseAttack
chosen
Indicates that an entity possesses a fundamental or default attack action or value used as its primary offensive capability.
-
E.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:18 p.m.