Triple
T37664964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying Obsidian |
E937799
|
entity |
| Predicate | redstoneInteraction |
P100824
|
FINISHED |
| Object | does not conduct redstone power |
—
|
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: does not conduct redstone power | Statement: [Crying Obsidian, redstoneInteraction, does not conduct redstone power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redstoneInteraction Context triple: [Crying Obsidian, redstoneInteraction, does not conduct redstone power]
-
A.
hasRedstoneInteraction
chosen
Indicates that there is some form of interaction or effect between the subject and a redstone-related mechanism or signal.
-
B.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
C.
isPoweredStructure
Indicates that a structure receives or is supplied with power (such as electricity or energy) enabling it to operate.
-
D.
controlInteraction
Indicates an interaction in which one entity directs, regulates, or constrains the behavior or state of another.
-
E.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.