Triple
T37664305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prismarine Bricks |
E937786
|
entity |
| Predicate | miningWithoutToolEffect |
P188646
|
FINISHED |
| Object | Drops nothing |
—
|
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: Drops nothing | Statement: [Prismarine Bricks, miningWithoutToolEffect, Drops nothing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningWithoutToolEffect Context triple: [Prismarine Bricks, miningWithoutToolEffect, Drops nothing]
-
A.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
B.
miningAllowed
Indicates that performing mining activities is permitted under the relevant rules or conditions.
-
C.
hasMiningCommodity
Indicates that an entity is associated with, produces, or contains a specific mining-related commodity.
-
D.
discoveryOfOre
Indicates the event or relationship in which a particular ore deposit is found, identified, or recognized, typically linking the discoverer, the ore, and the location or time of discovery.
-
E.
mineLevel
Indicates the depth or richness of mining activity or resources associated with an entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.