Triple
T37961144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shulker Shell |
E947010
|
entity |
| Predicate | craftingGridShape |
P190546
|
FINISHED |
| Object | one shell above chest and one shell below chest |
—
|
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: one shell above chest and one shell below chest | Statement: [Shulker Shell, craftingGridShape, one shell above chest and one shell below chest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: craftingGridShape Context triple: [Shulker Shell, craftingGridShape, one shell above chest and one shell below chest]
-
A.
craftingGrid
chosen
Indicates a relationship where items are arranged in a specific grid layout to be combined or crafted into a new item or outcome.
-
B.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
-
C.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
D.
grainShape
Indicates the characteristic form or contour of a grain or granular particle.
-
E.
coreShape
Indicates that one entity serves as the primary or central shape or geometric form of another entity.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:20 p.m.