Triple
T37664267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Prismarine |
E937785
|
entity |
| Predicate | canBePushedByPistons |
P100824
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [Dark Prismarine, canBePushedByPistons, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePushedByPistons Context triple: [Dark Prismarine, canBePushedByPistons, True]
-
A.
canBePushedForwardAlong
Indicates that something is capable of being transferred or mapped forward along a specified function, morphism, or direction while preserving the relevant structure or properties.
-
B.
canBeMotionedBy
Indicates that one entity is capable of being set into motion or activated by another entity.
-
C.
isPoweredStructure
Indicates that a structure receives or is supplied with power (such as electricity or energy) enabling it to operate.
-
D.
hasRedstoneInteraction
chosen
Indicates that there is some form of interaction or effect between the subject and a redstone-related mechanism or signal.
-
E.
canPickUpBlocks
Indicates that an entity has the ability to lift and carry blocks.
- 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_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:18 p.m.