Triple
T37961145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shulker Shell |
E947010
|
entity |
| Predicate | cannotBeUsedAsFuel |
P192336
|
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: [Shulker Shell, cannotBeUsedAsFuel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeUsedAsFuel Context triple: [Shulker Shell, cannotBeUsedAsFuel, true]
-
A.
cannotBeUsedAs
chosen
Indicates that one entity is not permitted or not suitable to serve the role, function, or purpose of another entity.
-
B.
cannotBeSmelted
Indicates that the subject cannot undergo smelting to be transformed or processed into another material or form.
-
C.
isCombustible
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
-
D.
isLessFlammableThan
Indicates that one entity has a lower tendency to catch fire or burn than another entity.
-
E.
fuelCharacteristic
Indicates a relationship where a fuel is associated with one of its defining properties or qualities, such as composition, performance, or behavior.
- 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_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:20 p.m.