Triple
T37661739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wither Skeleton Skull |
E937732
|
entity |
| Predicate | wearable |
P56501
|
FINISHED |
| Object | Can be worn in helmet slot by players |
—
|
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: Can be worn in helmet slot by players | Statement: [Wither Skeleton Skull, wearable, Can be worn in helmet slot by players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearable Context triple: [Wither Skeleton Skull, wearable, Can be worn in helmet slot by players]
-
A.
wearableBy
chosen
Indicates that one entity is designed or suitable to be worn on the body by another entity.
-
B.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
C.
wearerType
Indicates the type or category of entity that is intended to wear or use the associated item.
-
D.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
E.
wearIndicates
Indicates that one entity is wearing or has clothing or an accessory on its body, typically as a visible or functional item.
- 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_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.