Triple
T37665151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purpur Block |
E937803
|
entity |
| Predicate | canBePulledByPistons |
P200197
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Purpur Block, canBePulledByPistons, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePulledByPistons Context triple: [Purpur Block, canBePulledByPistons, Yes]
-
A.
cannotBePulledBy
Indicates that one entity is not capable of being pulled or dragged by another entity.
-
B.
canBePulledBackAlong
Indicates that a structure or object can be transferred or redefined along a given mapping or morphism so that it is compatible with that mapping.
-
C.
pistons
Indicates a mechanical relationship where pistons convert pressure (often from combustion or fluid) into linear motion or vice versa within an engine or similar system.
-
D.
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.
-
E.
hasPegMechanism
Indicates that one entity includes or uses a peg-based mechanism in relation to another entity.
- 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_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
| PDg | Predicate description generation | batch_69ff79e645c08190a974b5239efac35b |
completed | May 9, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.