Triple
T37661787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nether Star |
E937733
|
entity |
| Predicate | craftingRecipeOutput |
P91959
|
FINISHED |
| Object | 1 Beacon |
—
|
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: 1 Beacon | Statement: [Nether Star, craftingRecipeOutput, 1 Beacon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftingRecipeOutput Context triple: [Nether Star, craftingRecipeOutput, 1 Beacon]
-
A.
craftable
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
B.
craftingGrid
Indicates a relationship where items are arranged in a specific grid layout to be combined or crafted into a new item or outcome.
-
C.
craftingRarityCost
Indicates the resource cost required to craft an item at a given rarity level.
-
D.
productionOutcome
chosen
Indicates the result or consequence produced by a given production process, activity, or event.
-
E.
isCraftProduct
Indicates that something is a product created through skilled manual craftsmanship, often in small-scale or artisanal production rather than mass manufacturing.
- 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_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:18 p.m.