Triple
T37961135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shulker Shell |
E947010
|
entity |
| Predicate | maximumDropQuantityWithLooting |
P195030
|
FINISHED |
| Object | up to 4 per Shulker |
—
|
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: up to 4 per Shulker | Statement: [Shulker Shell, maximumDropQuantityWithLooting, up to 4 per Shulker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDropQuantityWithLooting Context triple: [Shulker Shell, maximumDropQuantityWithLooting, up to 4 per Shulker]
-
A.
maxDropChanceWithLootingIII
Indicates the highest possible chance that an item will drop when the looting level is III.
-
B.
lootValue
Indicates the total worth or value assigned to items obtained as loot in a given context or event.
-
C.
lootRestriction
Indicates a rule or limitation on what loot can be obtained, used, or distributed in a given context.
-
D.
lootDifficulty
Indicates how challenging it is to obtain loot from a given source or encounter.
-
E.
canPickUpLoot
Indicates that one entity is able to collect or take possession of loot associated with another entity or location.
- F. None of above. chosen
Provenance (4 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 3, 2026, 4:20 p.m.