Triple
T37665210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End rod |
E937804
|
entity |
| Predicate | canBePoweredByRedstone |
P100824
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [End rod, canBePoweredByRedstone, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePoweredByRedstone Context triple: [End rod, canBePoweredByRedstone, false]
-
A.
hasRedstoneInteraction
chosen
Indicates that there is some form of interaction or effect between the subject and a redstone-related mechanism or signal.
-
B.
isPoweredStructure
Indicates that a structure receives or is supplied with power (such as electricity or energy) enabling it to operate.
-
C.
hasPowerTerminal
Indicates that an entity is equipped with or connected to a power terminal through which electrical power can be supplied or distributed.
-
D.
hasEnergyInput
Indicates that an entity receives or requires a specified source or form of energy to operate or occur.
-
E.
suppliesPowerTo
Indicates that one entity provides electrical or energy power required for the operation or functioning 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff84df768c81908c65a1a7e33103ad |
completed | May 9, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69ff848d0af881908ee42c27a58af47e |
completed | May 9, 2026, 7:01 p.m. |
Created at: May 3, 2026, 4:18 p.m.