Triple
T37664244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Prismarine |
E937785
|
entity |
| Predicate | craftingIngredient |
P12771
|
FINISHED |
| Object | Prismarine Shard |
—
|
NE NERFINISHED |
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: Prismarine Shard | Statement: [Dark Prismarine, craftingIngredient, Prismarine Shard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftingIngredient Context triple: [Dark Prismarine, craftingIngredient, Prismarine Shard]
-
A.
craftable
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
B.
craftingWith
Indicates a relationship where something is created or shaped using a particular tool, material, or method.
-
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.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
E.
usesIngredient
chosen
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
- 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:18 p.m.