Triple
T37664962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying Obsidian |
E937799
|
entity |
| Predicate | cannotBePushedBy |
P192414
|
FINISHED |
| Object | pistons |
—
|
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: pistons | Statement: [Crying Obsidian, cannotBePushedBy, pistons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBePushedBy Context triple: [Crying Obsidian, cannotBePushedBy, pistons]
-
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.
cannotBeHeldBy
Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
-
C.
cannotBeRemovedBy
Indicates that one entity is not capable of removing, deleting, or otherwise eliminating another entity.
-
D.
cannotBeGraspedAs
Indicates that one entity is not capable of being mentally or conceptually understood in the manner or terms defined by another entity or perspective.
-
E.
cannotBeAwardedTo
Indicates that a particular entity is ineligible to receive a specified award, prize, or recognition.
- F. None of above. chosen
Provenance (4 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.