Triple
T37661729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wither Skeleton Skull |
E937732
|
entity |
| Predicate | craftingUsage |
P188346
|
FINISHED |
| Object | Required to craft the Wither structure |
—
|
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: Required to craft the Wither structure | Statement: [Wither Skeleton Skull, craftingUsage, Required to craft the Wither structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftingUsage Context triple: [Wither Skeleton Skull, craftingUsage, Required to craft the Wither structure]
-
A.
craftable
chosen
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
B.
craftingRarityCost
Indicates the resource cost required to craft an item at a given rarity level.
-
C.
craftingGrid
Indicates a relationship where items are arranged in a specific grid layout to be combined or crafted into a new item or outcome.
-
D.
craftingRarity
Indicates the rarity level associated with crafting an item or outcome within a system.
-
E.
craftedIn
Indicates that an object or work was created or produced at a particular place or within a specific location.
- 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.